Championship-grade repository maintenance. Audits for test artifacts, dependency issues, CI/CD health, documentation sync, and FAF alignment. Generates prioritized cleanup plans. Use when repos need deep cleaning or ongoing maintenance.
Championship-grade repository maintenance. Audits for test artifacts, dependency issues, CI/CD health, documentation sync, and FAF alignment. Generates prioritized cleanup plans. Use when repos need deep cleaning or ongoing maintenance.
Unused dependencies (installed but never imported)
3. CI/CD Alignment
# Workflow consistency check
Node versions across all workflows
Test matrices (should match across ci.yml, release.yml)
Action versions (@v6 vs @v5)
Failed/skipped workflow runs
Secrets/tokens properly configured
Common Fixes:
Remove EOL runtimes (e.g. Node 16) from release workflows
Align Node versions across all workflows (e.g. 18/20/22)
Pin packages that break under ESM resolution
4. Documentation Sync
# Context alignment check
README.md ↔ CLAUDE.md ↔ project.faf
CHANGELOG up to date with git tags
package.json version matches latest tag
Examples in README still work
Links not broken (404 checks)
FAF-Specific:
project.faf reflects current state
CLAUDE.md bi-sync active
.faf-dna not churning unnecessarily
5. Git Hygiene
# .gitignore audit
Untracked files that should be ignored
*.config.mjs
*.faf test artifacts
.env.local, .env.development
Large files in git history (use git-filter-repo)
Binary files that don't belong
Pattern Recognition:
# Add to .gitignore based on artifacts found
*.config.mjs
*.faf.backup
.faf-dna.tmp
test-*.faf
6. Code Quality Signals
# Quick health indicators
Dead code (unused exports via ts-prune or depcheck)
TODO/FIXME comments (track count, prioritize)
Commented code blocks (remove or document)
Console.log statements in production code
Hardcoded secrets/tokens
# MCP-specific checks
package.json has "mcp" field
Server implements required tools
Tests cover all tool endpoints
README has MCP installation instructions
Registry listing accurate (npm + MCP registry)
🛠️ Phase 2: Cleanup Plan Generation
After audit, generate prioritized task list:
# 🏎️ REPO HEALTH REPORT: faf-cli**Overall Score:** 85% ◇ Bronze
**Status:** Production-ready with minor cleanup needed
---
## 🚨 CRITICAL (Fix Now)### 1. Security: `open@10` breaking CI/CD-**Impact:** Release pipeline failing
-**Fix:** Pin to `open@8.4.2` ✅ FIXED
-**Effort:** 5 minutes
-**Auto-fix:** Available
---
## ⚠️ MEDIUM (This Week)### 3. .gitignore Gaps-**Issue:**`*.config.mjs`, `*.faf` test files not ignored
-**Fix:** Add patterns to .gitignore
-**Effort:** 1 minute
-**Auto-fix:** Available
```gitignore
*.config.mjs
test-*.faf
# 1. MCP-specific structure
package.json has "mcp" field
Server exports via index.ts
Tools properly registered
# 2. Registry compliance
Registry listing accurate (npm + MCP registry)
README has MCP install instructions
Works with Claude Desktop config
# 3. Tool coverage
Each tool has tests
Each tool has description
Error handling implemented
# 4. Version alignment
package.json version
git tag version
MCP registry version
npm published version
MCP Cleanup Checklist:
Remove test artifacts
Update dependencies
Align workflows (Node 18/20/22)
Verify MCP tools still work
Update README examples
Check CHANGELOG current
Verify published to npm
Confirm registry listing accurate
✪ Tier System (Aligned with FAF)
CRITICAL: Use Official FAF Tiers for All Scoring
Score
Tier
Symbol
Status
100%
Trophy
✪
Perfect — Gold Code
99%
Gold
★
Exceptional
95%
Silver
◆
Top tier
85%
Bronze
◇
Production ready
70%
Green
●
Solid foundation
55%
Yellow
●
Needs improvement
1%
Red
○
Major work needed
0%
White
♡
Empty
The score is deterministic — same input → same score, every time. FAF doesn't lie.
Note: 🍊 Big Orange is an HONOR, not a score or a badge. It recognizes sustained excellence across multiple criteria; it is never calculated from a single score.
