菜单
Summarize current progress and persist it to a dated session file so work resumes cleanly in a future session. Use before /compact, before ending a session, or at major milestones. Pairs with /resume-session.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | save-session |
| description | Summarize current progress and persist it to a dated session file so work resumes cleanly in a future session. Use before /compact, before ending a session, or at major milestones. Pairs with /resume-session. |
Goal: a future session (or a fresh context) can pick up exactly where this left off.
.claude/sessions/<YYYY-MM-DD>.md (append across the day).~/.claude/harness-claude/sessions/<YYYY-MM-DD>.md.Create the directory if needed. Append to today's file; don't pollute it with old work — start a new dated file per day.
# Session <date> — <project/feature>
## Goal / current objective
## What works (verified, with evidence: test names, commands, screenshots)
## What was tried and did NOT work (so we don't repeat it)
## Not yet attempted / remaining (the next concrete steps)
## Key decisions & files touched
## Open questions / blockers
This skill is also invoked automatically by the PreCompact and Stop hooks — keep the format stable so those writes stay consistent.