esper:audit
Comprehensive project audit — health, architecture, phase retrospective, and codebase quality. Produces a scannable report with actionable recommendations.
npx skills add majiayu000/claude-skill-registry --skill esper-audit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
You are performing a comprehensive project audit. The user's initial prompt (if any): $ARGUMENTS ## Step 1: Check setup Run `esperkit config check`. If it exits non-zero, tell the user to run `/esper:init` first and stop. Run `esperkit config get current_phase` to get the current phase slug. ## Step 2: Gather project data Read the following files: - `.esper/CONSTITUTION.md` - `.esper/esper.json` - `.esper/phases/<current_phase>.md` Run these commands to gather plan state: ```bash esperkit plan list --dir pending --format json ``` ```bash esperkit plan list --dir active --format json ``` ```bash esperkit plan list --dir done --format json ``` Run these commands for git history and dependency health: ```bash git log --oneline -20 ``` ```bash git log --oneline --since="2 weeks ago" | wc -l ``` ```bash npm audit --json 2>/dev/null || true ``` ```bash npx npm-check-updates --errorLevel 0 2>/dev/null || true ``` ## Step 3: Project Health Analyze the gathered data across four dimensions: **Constitution Alignment** - Cross-reference recent commits and shipped plans against the principles in `CONSTITUTION.md` - Flag any drift — work that contradicts or ignores stated principles **Phase Prog
- Step 1: Check setup
- Step 2: Gather project data
- Step 3: Project Health
- Step 4: Phase Retrospective
- Step 5: Dependency Health
- Step 6: Architecture Review
- Step 7: Codebase Quality Audit
- Step 8: Security Review
- Step 9: Developer Experience Review
- Step 10: API & Interface Consistency
- Step 11: Report and Actions
esperkit plan list --dir pending --format json esperkit plan list --dir active --format json esperkit plan list --dir done --format json git log --oneline -20 git log --oneline --since="2 weeks ago" | wc -l npm audit --json 2>/dev/null || true npx npm-check-updates --errorLevel 0 2>/dev/null || true
What does the esper:audit skill do?
Comprehensive project audit — health, architecture, phase retrospective, and codebase quality. Produces a scannable report with actionable recommendations.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill esper-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
