agentleFS
NoaiRoxNoaiRox/specialist-agent/skills/health/SKILL.md

health

Skill2 starsChanged 9 months agoMITView on GitHub

Use when assessing overall project quality, onboarding onto a new codebase, or before major refactoring to establish a baseline.

55 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use plan-tune, ios-clean and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ShreyRaviSkill

    plan-tune

    Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). Review which AskUserQuestion prompts fire across gstack skills, set per-question preferences (never-ask / always-ask / ask-only-for-one-way), inspect the dual-track profile (what you declared vs what your behavior suggests), and enable/disable question tuning. Conversational interface — no CLI syntax required.

    Also in 9 projects that use this

  • Saqlain-811Skill

    ios-clean

    Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)

    Also in 5 projects that use this

  • Saqlain-811Skill

    ios-fix

    Autonomous iOS bug fixer. (gstack)

    Also in 5 projects that use this

  • seek888Skill

    pair-agent

    Pair a remote AI agent with your browser. One command generates a setup key and prints instructions the other agent can follow to connect. Works with OpenClaw, Hermes, Codex, Cursor, or any agent that can make HTTP requests. The remote agent gets its own tab with scoped access (read+write by default, admin on request). Use when asked to "pair agent", "connect agent", "share browser", "remote browser", "let another agent use my browser", or "give browser access". (gstack) Voice triggers (speech-to-text aliases): "pair agent", "connect agent", "share my browser", "remote browser access".

    Also in 11 projects that use this

  • ShreyRaviSkill

    landing-report

    Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)

    Also in 8 projects that use this

  • timurgaleevSkill

    document-generate

    Generate missing docs for a feature, module or project as tutorials, how-tos, reference and explanation.

    Also in 7 projects that use this

  • +1 more from Saqlain-811
  • +2 more from ShreyRavi

The file

Files
SKILL.md

/health - Project Health Score

Generate a comprehensive health score for your project or a specific module.

Scope: $ARGUMENTS (default: full project)

Scoring Categories

CategoryWeightWhat it measures
Architecture25%ARCHITECTURE.md conformance
Tests20%Coverage, test presence
Security20%OWASP compliance, secrets
Performance15%Bundle size, caching
Maintainability20%Code complexity, docs

Workflow

Step 1: Gather Metrics

# File counts
find src -name "*.ts" -o -name "*.tsx" | wc -l
find src -name "*.test.ts" -o -name "*.spec.ts" | wc -l

# TypeScript check
npx tsc --noEmit 2>&1 | grep -c "error"

# Test coverage (if available)
npm test -- --coverage --json 2>/dev/null

# Bundle analysis
npm run build 2>&1 | grep -E "size|chunk"

# Security checks
grep -rn "dangerouslySetInnerHTML\|v-html\|eval(" src/ 2>/dev/null | wc -l
grep -rn "password\|secret\|token" src/ --include="*.ts" 2>/dev/null | wc -l

Step 2: Calculate Scores

Architecture Score (25 points)

+5  ARCHITECTURE.md exists
+5  Module structure follows patterns
+5  No cross-module imports
+5  Correct layer usage (service→adapter→hook→component)
+5  Naming conventions followed

Test Score (20 points)

+5  Test files exist
+5  Coverage > 50%
+5  Coverage > 70%
+5  Coverage > 80%
+5  All tests passing
-2  Each failing test

Security Score (20 points)

+5  No hardcoded secrets
+5  No dangerous HTML methods
+5  Input validation present
+5  Auth implementation exists
+5  Secure headers configured
-5  Each critical vulnerability

Performance Score (15 points)

+5  Lazy loading implemented
+5  Query caching present (staleTime)
+5  Bundle < 500KB
+5  No N+1 queries detected
-3  Each performance warning

Maintainability Score (20 points)

+5  README.md exists
+5  Files < 200 lines (average)
+5  Low cyclomatic complexity
+5  TypeScript strict mode
+5  No 'any' types
-2  Each 'any' type found

Step 3: Generate Report

Output Format

═══════════════════════════════════════════════════════════════
                    PROJECT HEALTH REPORT
═══════════════════════════════════════════════════════════════

   ██████████████████████████████████████░░░░░░░░  78/100

═══════════════════════════════════════════════════════════════

CATEGORY BREAKDOWN
───────────────────────────────────────────────────────────────

Architecture    ████████████████████░░░░░  20/25
  ✓ ARCHITECTURE.md exists
  ✓ Module structure correct
  ✗ Cross-module imports found (3 violations)
  ✓ Layer usage correct
  ✓ Naming conventions followed

Tests           ████████████████░░░░░░░░░  16/20
  ✓ Test files exist (42 specs)
  ✓ Coverage: 72%
  ✗ Coverage < 80% target
  ✓ All tests passing

Security        █████████████████████████  20/20
  ✓ No hardcoded secrets
  ✓ No dangerous HTML methods
  ✓ Input validation present
  ✓ Auth implementation exists
  ✓ Secure headers configured

Performance     █████████████░░░░░░░░░░░░  10/15
  ✓ Lazy loading implemented
  ✗ Missing staleTime in 5 queries
  ✓ Bundle: 320KB
  ✗ Potential N+1 in user.service.ts

Maintainability ████████████░░░░░░░░░░░░░  12/20
  ✓ README.md exists
  ✗ 3 files > 200 lines
  ✓ Low complexity
  ✓ TypeScript strict mode
  ✗ 12 'any' types found

═══════════════════════════════════════════════════════════════

TOP ISSUES TO FIX (by impact)
───────────────────────────────────────────────────────────────

1. 🔴 [Architecture] Cross-module imports
   Files: src/modules/orders/components/UserCard.tsx
   Fix: Move shared components to src/shared/

2. 🟡 [Performance] Missing staleTime in queries
   Files: src/modules/*/hooks/use*.ts (5 files)
   Fix: Add staleTime to all useQuery calls

3. 🟡 [Maintainability] Files exceeding 200 lines
   Files: src/modules/auth/components/LoginForm.tsx (284 lines)
   Fix: Split into smaller components

4. 🟡 [Tests] Coverage below 80%
   Current: 72%
   Fix: Add tests for uncovered modules

═══════════════════════════════════════════════════════════════

TREND (if previous scans exist)
───────────────────────────────────────────────────────────────

  Previous: 71/100 (2024-01-10)
  Current:  78/100 (2024-01-20)
  Change:   +7 points ↑

═══════════════════════════════════════════════════════════════

RECOMMENDATIONS
───────────────────────────────────────────────────────────────

  @reviewer  - Run /review-fix-violations to auto-fix
  @tester    - Add tests for auth module
  @builder   - Refactor LoginForm.tsx

═══════════════════════════════════════════════════════════════
  Generated: 2024-01-20 14:30 | Scan time: 12s
═══════════════════════════════════════════════════════════════

Score Interpretation

ScoreGradeStatus
90-100AExcellent
80-89BGood
70-79CAcceptable
60-69DNeeds Work
0-59FCritical

Save History

Save scan to .claude/health-history.json:

{
  "scans": [
    {
      "date": "2024-01-20T14:30:00Z",
      "score": 78,
      "categories": {
        "architecture": 20,
        "tests": 16,
        "security": 20,
        "performance": 10,
        "maintainability": 12
      }
    }
  ]
}

Quick Mode

For fast feedback (< 5 seconds):

/health quick

Only checks:

  • TypeScript errors
  • Test status
  • File count

Anti-Rationalization

ExcuseReality
"The score doesn't matter, the app works"Working today doesn't mean maintainable tomorrow. The score measures long-term health.
"We'll improve the score after the deadline"After the deadline there's another deadline. Measure now, fix incrementally.
"80% coverage is overkill"80% is the baseline. Below that, regressions hide in untested code.
"Security checks are paranoid"One vulnerability costs more than 100 health scans. Paranoia is appropriate.

Rules

  1. Be objective - Numbers, not opinions
  2. Prioritize issues - Most impactful first
  3. Show trends - Compare to previous scans
  4. Actionable - Suggest specific fixes
  5. Save history - Track progress over time

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.