Menu
Confirmed commit/push/PR pipeline — stage, commit, push, open a PR. Never runs unattended; every destructive or outward-facing step is confirmed first.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | ship |
| description | Confirmed commit/push/PR pipeline — stage, commit, push, open a PR. Never runs unattended; every destructive or outward-facing step is confirmed first. |
| disable-model-invocation | true |
git status, git diff, git diff --cached, git log -5 --oneline. Summarize what's about to be shipped..claude/harness.env; run $BUILD_CMD, $TEST_CMD, $LINT_CMD (each that is set), plus bash .claude/hooks/tests/run-all.sh and bash .claude/evals/regressions/run-all.sh if the diff touches the harness itself. Do not proceed to stage/commit if any fail — report and stop..env*, secret-shaped files, lockfile hand-edits, build output, OS junk. Draft a commit message matching this repo's existing style (Conventional Commits per .claude/rules/git-workflow.md if present). Ask for confirmation before running git commit.TASKS.md item, move it to ARCHIVE.md with a verification line per .claude/rules/ship-verification.md — verified end-to-end, not just compiled.gh is available and a remote exists. Check for an existing PR via gh pr view first. Draft title (<72 chars) and body (Summary + Test plan) from the full commit range. Ask for confirmation before creating.Hard rules: never skip a confirmation step, never --force push, never commit content the secret scanner flagged without explicit user override, never push directly to a protected branch.