Project health check

Skill PIXARTSeu/Synapse/packages/codegraph/data/skill/project-health-check

Self-improving AI brain for Claude Code & Desktop — 28 MCP tools, 253 skills, collective memory, project tracking, work logs. One server, all your sessions share the same knowledge. Deploy on Coolify in 2 minutes.

Install

npx -y skills add PIXARTSeu/Synapse --skill project-health-check

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Comprehensive health check of a Next.js/Payload CMS project. Use when user asks to "check the project", "audit the codebase", "what's the state of the project", "project health", or before a major release. Checks TypeScript errors, build status, missing env vars, i18n completeness, SEO basics, and Payload CMS configuration.

SKILL.md

3.3 KB, as published. Nobody here has run it

Project Health Check

Analisi completa della salute di un progetto Next.js + Payload CMS.

Overview

Verifica 8 aree critiche e produce un report con score e raccomandazioni.

Core principle: Evidence-based assessment — solo dati reali, nessuna assunzione.

Checks

1. TypeScript & Build

npm run build 2>&1 | tail -20
npm run typecheck 2>&1 | head -30

Check: zero errori TS, build passa

2. Lint

npm run lint 2>&1 | head -20

Check: zero errori lint

3. Environment Variables

Leggi .env.example o AGENTS.md per lista env vars attese. Verifica che .env.local (o env del deployment) le contenga tutte.

4. i18n Completeness

ls messages/

Verifica che tutti i file locale (it.json, en.json, cs.json) esistano e abbiano le stesse chiavi.

5. SEO Basics

grep -r "generateMetadata\|metadata" src/app --include="*.tsx" -l

Check: ogni page.tsx ha metadata, robots.ts e sitemap.ts esistono.

6. Payload CMS

grep -r "collections" src/payload.config.ts 2>/dev/null | head -5

Check: config Payload presente, collections definite.

7. Performance

ls public/

Check: no immagini >500KB in public/, next/image usato dove serve.

8. Security

grep -r "console.log\|debugger" src --include="*.ts" --include="*.tsx" -l 2>/dev/null | head -5

Check: no console.log in produzione, secret keys non hardcoded.

Report Format

PROJECT HEALTH REPORT
=====================
Project: [nome]
Date: [data]

SCORES:
✅ TypeScript/Build   [PASS/FAIL]
✅ Lint               [PASS/FAIL]  
⚠️  Environment Vars  [X/Y vars present]
✅ i18n               [IT/EN/CS present]
⚠️  SEO               [X/Y pages with metadata]
✅ Payload CMS        [PASS/FAIL]
✅ Performance        [PASS/FAIL]
✅ Security           [PASS/FAIL]

OVERALL: [score]/100

CRITICAL ISSUES:
- [lista problemi critici]

RECOMMENDATIONS:
- [lista miglioramenti]

Examples

Example 1: Pre-release check

User: "Check the project before we deploy"

Project health check:

Runs build → PASS
Checks i18n → cs.json missing 3 keys
Checks SEO → /contatti page missing metadata
Report: 75/100, 2 recommendations before deploy

Example 2: New project setup

User: "What's the state of this new project?"