القائمة
Run all audit skills — perf-audit, test-audit, doc-audit, wiki-audit, dependency-audit — in parallel on isolated worktrees. Use when you want a full project health check or before a release.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | audit |
| description | Run all audit skills — perf-audit, test-audit, doc-audit, wiki-audit, dependency-audit — in parallel on isolated worktrees. Use when you want a full project health check or before a release. |
Run all 5 audit skills in parallel on isolated git worktrees for a comprehensive project health check.
Launch all 5 audit skills simultaneously, each on its own worktree. Each skill creates its own branch, PR, and merges independently via /ship.
Spawn 5 agents in a single message (so they run concurrently), each with isolation: "worktree" and mode: "bypassPermissions". Each agent prompt should:
.claude/skills/perf-audit/SKILL.md)Agent 1 — perf-audit → Read .claude/skills/perf-audit/SKILL.md, execute it fully
Agent 2 — test-audit → Read .claude/skills/test-audit/SKILL.md, execute it fully
Agent 3 — doc-audit → Read .claude/skills/doc-audit/SKILL.md, execute it fully
Agent 4 — wiki-audit → Read .claude/skills/wiki-audit/SKILL.md, execute it fully
Agent 5 — dependency-audit → Read .claude/skills/dependency-audit/SKILL.md, execute it fully
Important: Since agents run on isolated worktrees, they won't conflict with each other even if they touch overlapping files. Each PR merges independently.
Each agent should receive a prompt like:
You are running a full audit of the Quest codebase. Read the skill file at
.claude/skills/{name}/SKILL.mdand follow its instructions completely. You are working in an isolated git worktree.Key requirements:
- Follow every phase described in the skill file
- Create a branch named
{name}-YYYYMMDD(use today's date)- Commit all changes with a descriptive message
- Push the branch and create a PR with automerge enabled (
gh pr merge --auto --squash)- Wait for CI to pass and the PR to merge
- If CI fails, fix the issues and push again
- Return: (1) summary of findings, (2) fixes applied, (3) PR URL and merge status
After all 5 agents complete, compile and report a summary table:
| Audit | Findings | Fixes | PR | Status |
|---|---|---|---|---|
| perf-audit | ... | ... | #N | merged/pending |
| test-audit | ... | ... | #N | merged/pending |
| doc-audit | ... | ... | #N | merged/pending |
| wiki-audit | ... | ... | #N | merged/pending |
| dependency-audit | ... | ... | #N | merged/pending |
Evaluates the accuracy and scope coverage of the other audit skills (perf-audit, test-audit, doc-audit, wiki-audit, dependency-audit) by re-verifying past findings against source and checking for scope drift, then safely improves their SKILL.md files. Use when asked to evaluate audit skill performance, or auto-triggered by a domain audit skill after its 5th run since the last evaluation.
Multi-agent dependency health audit — finds outdated versions, unused deps, security issues, and over-specified features. Use when dependencies are stale, after adding deps, or before releases.
Multi-agent wiki audit — finds stale numbers, missing systems, and broken links in the player-facing wiki. Use when wiki is stale, after game changes, or before releases.
Multi-agent developer documentation audit — finds stale constants, missing files, and outdated types across CLAUDE.md files, README.md, and docs/. Use when docs are stale, after adding features, or before releases.
Multi-agent test health audit — finds flaky tests and performance bottlenecks by area, auto-fixes safe patterns, and verifies with 10x runs. Use when tests are flaky, slow, or before releases.
Drive the real game in tmux against fixture save states, inspect PNG screenshots or short video recordings of the rendered TUI to verify your own UI changes, and iterate until they render correctly. Use PROACTIVELY after any change to src/ui/, when asked to "screenshot the game", "record the game", "show me the change/transition/animation", "drive the game", or before opening a PR that touches UI.