Install in Claude Code
Copygit clone --depth 1 https://github.com/kentcdodds/kody /tmp/cleanup-after-migrations && cp -r /tmp/cleanup-after-migrations/.agents/skills/cleanup-after-migrations ~/.claude/skills/cleanup-after-migrationsThen start a new Claude Code session; the skill loads automatically.
Definition
SKILL.md
# Cleanup after migrations
Read
[`docs/contributing/cleanup-after-migrations.md`](../../../docs/contributing/cleanup-after-migrations.md).
Do not leave untracked cruft.
## Decision
1. **Do it now** when the leftover is safe to drop with this change.
2. **Open a GitHub issue** when it must wait on a later migration, a second
deploy, a soak or metrics gate, a fleet apply, or another cutover.
A runbook or `TODO` is not the tracker. The issue is.
Search open `Cleanup:` issues first. Title:
`Cleanup: <what to remove> after <gate>`. Label: `improvement`. Link the issue
from the introducing PR.
```markdown
## Leftover
What to delete or stop serving.
## Why it waits
The gate.
## Ready when
A falsifiable criterion (not a calendar date alone).
## How to verify
Commands, queries, or deploy evidence.
## Introduced by
PR that added the leftover.
```
```bash
gh issue create --title "Cleanup: … after …" --label improvement --body-file -
```
Or `kody:@kentcdodds/github/request` `POST /repos/kentcdodds/kody/issues`.
Soak or calendar gates also get a scheduled wake (`execute` +
`workflows.create({ runAt, idempotencyKey })`) per
[ship-pr](../ship-pr/SKILL.md). Close the issue when the cleanup lands.More from this repository
conductSkill
>
control-kodySkill
>
orchestrateSkill
>
remixSkill
Build and review Remix 3 applications using the `remix` npm package and
ship-prSkill
>
testing-multi-worker-devSkill
How to run and test kody's multi-worker local dev (origin kody worker +
visual-recapSkill
Generate and maintain the system recap block in a PR description - a