update-docs

Update Docs

Scan the TrueMatch codebase and update all documentation to reflect the current state of the code.

Live Context

Recent commits: !git log --oneline -20 2>/dev/null || echo "(no git history)"

Files changed since last tag (or last 10 commits if no tags): !git diff --name-only $(git describe --tags --abbrev=0 2>/dev/null || git rev-parse HEAD~10 2>/dev/null || echo HEAD) HEAD 2>/dev/null | head -40 || echo "(could not determine changed files)"

Scope requested: $ARGUMENTS (if empty, run all sections)

---

What This Skill Does

1. Audits every docs/ file against the actual codebase
2. Regenerates stale auto-managed sections using <!-- GENERATED:START/END --> markers
3. Leaves all <!-- MANUAL:START/END --> blocks and unmarked narrative untouched
4. Creates stub files for expected docs that don't exist yet
5. Prints a structured summary of every change made

---

Step 1 — Inventory the Codebase

Read the following and build an internal picture of what exists:

Code:

• api/routes/ — every route file: HTTP methods, paths, handler names, JSDoc summaries
• api/middleware/ — every middleware: what it does, headers/errors it handles
• skill/ — skill.md and any supporting files: what protocol it defines
• Root: README.md, CONTRIBUTING.md, package.json (or equivalent manifest)

Docs:

• docs/ — every file (note which have <!-- GENERATED --> markers and which don't)
• .claude/agents/ — agent definition files (name and description frontmatter)

For each source file extract:

• Exported functions / route handlers / middleware names
• JSDoc / docstring summaries if present
• File-level purpose comment if present

---

Step 2 — Evaluate Each Doc File Against the Doc Contract

docs/architecture.md

Auto-maintained sections:

• Directory tree of all non-trivial project files (regenerate from filesystem every run)
• One-line description of each top-level directory's purpose
• Data flow diagram in ASCII or Mermaid: agent → API → matching logic → notification