audit
01Command Claude Code
Run docs-checker and portfolio-audit in parallel on the current project. Optionally specify a canonical URL.
Claude Code hooks, agents and commands for running 10+ personal apps without babysitting every diff — MIT, 2 blocking hooks included.
This repository also configures its own agents. See what claude-code-setup tells them →
Command Claude Code
Run docs-checker and portfolio-audit in parallel on the current project. Optionally specify a canonical URL.
Command Claude Code needs its repo
Sweep /.claude disk hygiene to stated retentions, clean up stale plans from repos, audit plugin health, and compact agent memory files.
Command Claude Code
Scaffold a new app in /Dev with full portfolio compliance from day one.
Command Claude Code needs its repo
Sync the claude-code-setup repo from live /.claude/ config. Copies, anonymizes and redacts private regions, cleans stale files, updates README counts, updates workflow guide, audits for leaks. Refuses to overwrite hand-edited destinations.
Command Claude Code
Monthly technical health review in two phases. Phase 1: fast triage across ALL portfolio apps — scores each app on commit activity, portfolio prominence, time since last scan, and detected issues. Proposes a priority order. Phase 2: deep review on the apps the owner selects. Run without args for the full flow, or skip…
Command Claude Code
New-model setup review — derive every model pin and headless job from the tree, add the new model's effort entry, re-test prompts and design scaffolding tuned for the previous model. Proposes; commits nothing without the owner.
Command Claude Code
Take a plan from review to reviewed code — review, fold findings, stop for owner approval, execute, code-review, stop before push. Owns the sequencing and the approval stop only.
Command Claude Code
Audit the rendered design of live sites. Evidence capture first, then one critique per site. Argument is a URL, a repo name, or all.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: