メニュー
Use when touching code without reliable automated tests or with nondeterminism such as time, randomness, or I/O.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/shunta-sato/agent-instructions-playbook --skill working-with-legacy-codeコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Use when finishing a branch or PR after verification and review, including merge, PR publication, keep, discard, cleanup, local sync, and reporting merge or PR URLs with current git state.
Use when fixing or investigating crashes, regressions, flakes, hangs, incorrect outputs, or incidents.
Use when work is complex, long-running, multi-step, cross-boundary, likely to span multiple PRs/sessions, or needs handoff-ready planning under plans/.
SKILL.md を表示中
SOC 職業分類に基づく
| name | working-with-legacy-code |
| description | Use when touching code without reliable automated tests or with nondeterminism such as time, randomness, or I/O. |
| metadata | {"short-description":"Working with legacy code safely","requires":["references/working-with-legacy-code.md"],"resources":["references/working-with-legacy-code-cpp.md","references/working-with-legacy-code-py.md","references/working-with-legacy-code-ts.md"]} |
Use this skill to change legacy code safely: code with weak tests, no tests, or behavior that is hard to make deterministic.
The goal is not to “make it perfect” immediately. The goal is to create safety, then change behavior in small steps. Rewrite is a last resort after characterization, seams, and small refactors are insufficient.
Invoke this skill before refactoring if any of the following is true:
Open references/working-with-legacy-code.md. Pick the headings that match your situation and follow the order.
references/working-with-legacy-code-cpp.mdreferences/working-with-legacy-code-py.mdreferences/working-with-legacy-code-ts.mdCreate a safety net first:
Only after the safety net is green:
build / format / static analysis / tests green at every step.Treat rewrite as a last resort. If proposed, record why characterization + seams + small refactors are insufficient, which accumulated behaviors stay protected, and the rollback path.
If you cannot add a safety net, stop and explain why. Provide a reproducible manual procedure and the risk.
## Legacy Change Safety Record
- Touched behavior:
- Existing coverage:
- Safety-net test(s):
- Characterized current behavior:
- Preserved behavior / accumulated edge cases:
- Introduced seam(s):
- Refactor sequence:
- Intended behavior change:
- Rewrite avoided or justified:
- Verification commands/results: