菜单
Holistic, single-pass senior-engineer review of the target project's actual code (not the harness) across security, performance, code quality, and production-readiness. Use for 'is this ready to ship', a full code review, a security audit, or a performance pass.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create or upgrade a self-improving Claude Code harness in the current project — self-healing failure ledger, per-file lesson memory, regression evals, small-model elevation agents, deterministic safety hooks. Modes: (no args) auto-detect new vs upgrade; 'doctor' = validate only. Evidence-gated: scan, propose plan, confirm, apply, verify.
Self-maintenance pass over the .claude/ harness itself: validate every mechanical invariant, detect drift and dead weight, and propose upgrades. Run periodically, after any harness change, or via /loop.
Run one iteration of this project's maintenance loop: finish in-flight work, convert failures into lessons, checkpoint hygiene, audit the harness, or start the next pending task — whichever is highest-value right now. Also the remedy when capability-gate.sh blocks a source edit because maintenance is overdue.
Remove dead code, unused dependencies, commented-out blocks, and orphaned files once a checkpoint is reached — for long-term maintainability. Evidence-gated and reversible: nothing is removed without proof it is unreferenced, and build+tests must stay green after every batch. Run after a milestone/feature completes, not mid-implementation.
Convert this session's failures and user corrections into durable per-file lessons in .claude/memory/lessons/, following the evidence-backed write policy (retrieve-similar-first, delta updates, weighted vote lifecycle, hook promotion). Run at the end of any session that contained a correction or a repeated failure.
Structured debugging flow — check issues-solved/ first, reproduce, fix the root cause, verify end-to-end, and capture a new issues-solved entry if it was non-trivial. Use when a bug is reported or a test fails unexpectedly.
| name | senior-review |
| description | Holistic, single-pass senior-engineer review of the target project's actual code (not the harness) across security, performance, code quality, and production-readiness. Use for 'is this ready to ship', a full code review, a security audit, or a performance pass. |
This is a read-only, single holistic pass over real project code — distinct from /harness-audit (which only audits .claude/ itself) and from the gated multi-agent reviewer pipeline (code-reviewer/security-reviewer/silent-failure-hunter agents, review-diff.js), which this complements rather than replaces.
Build a mental model of the system before judging any line of it: read CLAUDE.md and .claude/harness.env for the stack, build/test/lint commands, and any documented exclusions (e.g. "no browser frontend here" makes XSS checks N/A) — don't duplicate that orientation into a separate file, it already has one source of truth.
Read the matching reference file when you reach that phase — don't hold all four checklists in your head at once, that's exactly the token cost references/ avoids:
references/security.mdreferences/performance.mdreferences/code-quality.mdreferences/production-readiness.mdSeverity scale for every finding: see references/severity.md — the same scale every reviewer in this harness cites, so verdicts stay consistent across tools.
Where: file:line
What: the issue
Impact: concrete consequence — quantify it if you can ("at 1M rows this times out," not "this could be slow")
Fix: the specific change (a snippet if non-trivial)
Confidence: 0-100
references/production-readiness.md's checklist as [ ]/[x] rows)Do not modify any files. Report findings only.