菜单
Load the most recent session file and re-establish context at the start of a new session. Use when continuing multi-session work. Pairs with /save-session.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | resume-session |
| description | Load the most recent session file and re-establish context at the start of a new session. Use when continuing multi-session work. Pairs with /save-session. |
Goal: restore working context cheaply, without re-exploring.
.claude/STATE.md (schema:
docs/state-and-artifacts.md). Its frontmatter gives the machine-navigable position in
one read: phase, status, slug, next_skill. If a slug is set, glance at
.claude/planning/<slug>/ (SPEC.md / PLAN.md / VERIFICATION.md) for the current
artifacts. If STATE.md is absent, skip to the session file — the spine is optional..claude/sessions/ in the repo, else ~/.claude/harness-claude/sessions/.next_skill says
/harness-claude:implement but the narrative describes shipping), flag the drift and reconcile from
the repo — do not trust either blindly.next_skill, cross-checked against
the narrative's "remaining"), and confirm with the user.The SessionStart hook already surfaces STATE's next_skill (or a pointer to the latest
session file) automatically; this skill is the full, deliberate restore. Treat every file
as what was true when written — verify before trusting specifics (files/flags may have
changed).
Bug-fix fast lane — the entry point for fixing something already broken (a red test, a prod error, a reported defect), not building a new feature. Does the bug-specific part — reproduce as a failing test, find the root cause, write a minimal fix-plan — then hands off to the existing pipeline (/implement → /review → /security-review → /verify → /ship) so the fix rides the proven gates. The non-negotiable discipline: reproduce as a failing test FIRST, fix minimally. Opt-in; invoked explicitly. Use when something is broken and you want it fixed under the harness's gates without over-ceremonying it through /spec.
Execute a plan via test-driven development — write tests first, then minimal code, phase by phase. Use after /plan (and /architect if needed) to write the actual feature. Delegates to the harness-claude:tdd-guide agent.
Review changed code for quality, correctness, and maintainability before merge. Use immediately after implementing or modifying code. Delegates to the harness-claude:code-reviewer agent. First gate of the Verify phase.
Confirm the change actually works by running the app/feature and observing real behavior — not just that tests pass. Use late in the Verify phase, before ship. Closes the loop between "tests green" and "it works."
Orchestrate the entire IMPLEMENT phase — test-driven implementation of the approved plan, resolving build/type errors as they arise. Use after /harness-plan. Sequences /implement and /build-fix, delegates to subagents, and halts if reality diverges from the plan.
Orchestrate the entire PLAN phase in one command — spec, research, plan, plan-check, and (if warranted) architecture. Use at the start of any non-trivial feature/change. Sequences the atomic skills, delegates to subagents, and pauses for your input at each decision gate.