List implementation follow-up and tests in Claude Code
Record technical debt, missing edge cases, and related changes after implementation, then list unit, integration, and edge tests that remain.
中文Install in Claude Code
A Claude Code project with notes from a completed change. This example prepares a follow-up checklist.
- Review `.claude/skills/post-implementation-checklist/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.claude/skills/post-implementation-checklist/` in your project and save the reviewed file as `.claude/skills/post-implementation-checklist/SKILL.md`.
- Start Claude Code from that project's root, then select `/post-implementation-checklist` in the slash menu.
Example task
The event list has just added venue filtering. The notes say `{feature:'venue-filter',debt:'duplicate label mapping',edge:'empty venue',integration:'print view'}`. The print view still ignores the filter, and leaving the venue empty must show every event.What to check
List `[duplicate label mapping, print view]` as debt and related work. Add three tests: a unit check for venue matching, a print view integration check for the chosen filter, and an empty-venue case that retains every event.
Original SKILL.md on GitHub · Updated
Frequently asked question
What tests should a feature checklist include after implementation?
List known debt and omissions. Choose unit and integration checks that fit the change and name the expected result for edges such as empty input.