Book Legacy Change Safety

Guides safe changes to legacy or weakly tested code by characterizing behavior before editing. In strict tasks, mandatory before the first behavior-changing edit for existing-behavior bug fixes or existing code with unclear behavior, low coverage, hidden dependencies, or high regression risk; in default/lite tasks, use on demand when those risks or explicit delivery requirements are present.

559 stars 13 forksProductivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add KunoLu/640-skills --skill book-legacy-change-safety
Manual install
git clone --depth 1 https://github.com/KunoLu/640-skills.git /tmp/640-skills
mkdir -p ~/.claude/skills
cp -r /tmp/640-skills/sbtd-workflow-onboard/templates/skills/book-legacy-change-safety ~/.claude/skills/book-legacy-change-safety

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Book Legacy Change Safety

Use this Skill when the main risk is not the requested change itself, but the uncertainty around existing behavior.

It is derived from the `mini` rule style of `agent-rules-books` and is intended to complement `diagnosing-bugs`, `tdd`, source/LSP/contract impact analysis, and project validation.

## Strict Development Gate

In a strict task, run this Skill before the first behavior-changing edit when either condition is true:

- The task fixes a bug in existing observable behavior.
- Existing target code has weak / missing tests, unclear or undocumented behavior, hidden dependencies, or high regression risk.

Emit a separate visible review:

```text
Legacy Change Safety Review
Status: characterized | needs-safety-net | seam-required | blocked
Behavior to change: ...
Behavior to preserve: ...
Current reproduction evidence: ...
Safety net: ...
Hidden dependencies / seam: ...
Validation plan: ...
Review mode: normal | safety-seam-only
```

- `characterized`: current behavior was reproduced or otherwise established, preserved behavior is explicit, and an adequate safety net exists.
- `needs-safety-net`: the safety net can be added without production-code edits; add or select the smallest characterization / regression check, then rerun this Skill.
Read the full skill on GitHub

Details

Skill name
book-legacy-change-safety
Path
sbtd-workflow-onboard/templates/skills/book-legacy-change-safety/SKILL.md
License
Apache-2.0
Repo updated
13 November 2026

FAQ

What does the Book Legacy Change Safety skill do?

Guides safe changes to legacy or weakly tested code by characterizing behavior before editing. In strict tasks, mandatory before the first behavior-changing edit for existing-behavior bug fixes or existing code with unclear behavior, low coverage, hidden dependencies, or high regression risk; in default/lite tasks, use on demand when those risks or explicit delivery requirements are present.

How do I install the Book Legacy Change Safety skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add KunoLu/640-skills --skill book-legacy-change-safety. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Book Legacy Change Safety popular?

It lives in KunoLu/640-skills, which has 559 GitHub stars and 13 forks.

Related skills

Handoff

559

KunoLu/640-skills

Compact the current conversation into a handoff document for another agent to pick up.

AI, LLMs & AgentsIn 2 lists13

Codebase Design

559

KunoLu/640-skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

Software DevelopmentIn 2 lists13

Diagnosing Bugs

559

KunoLu/640-skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

Software DevelopmentIn 2 lists13

Ponytail

559

KunoLu/640-skills

Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.

Productivity & Notes13

Book Ddia Data Design

559

KunoLu/640-skills

Guides data-intensive design checks for consistency, reliability, schema evolution, and data flow risks. In strict tasks, mandatory before design stabilizes or implementation begins when changing persisted/shared data, schemas, migrations, shared/persistent/cross-request/cross-process caches, async or cross-service flows, data ownership, or recovery; in default/lite tasks, use on demand when those risks or explicit delivery requirements are present.

Productivity & Notes13

Sbtd Task

559

KunoLu/640-skills

Use for SBTD task execution and continuation, explicit default/lite/strict mode selection, task records and status changes, cross-session recovery, and task handoffs. Load strict gates only for strict tasks; ordinary questions and read-only work do not create task files.

Productivity & Notes13

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.