メニュー
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.
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.
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.
| name | fix-issue |
| description | 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. |
| argument-hint | [symptom or error message] |
| disable-model-invocation | true |
The "issue" is whatever symptom/error the user describes: $ARGUMENTS.
.claude/issues-solved/INDEX.md for keywords from the symptom. On a match, read the linked entry and apply the known fix instead of re-deriving it..claude/rules/..claude/rules/ship-verification.md: re-run the reproduction (now passing), then the full test command from .claude/harness.env, then — if the bug was in a runtime path — actually run the affected behavior and inspect real output..claude/issues-solved/TEMPLATE.md to NNNN-slug.md (include "Failed attempts"), prepend a row to INDEX.md. If it's a behavior/process mistake rather than a code recipe, run /learn instead.TASKS.md/status.json if this bug blocked a tracked task.Hand off to /ship when done; don't self-commit as part of this skill.