control-kody

Drive and verify the Kody app with a Feature Map and one CLI. Use when changing UI, account routes, preview deploys, or proving a Cloud Agent change with a real origin, session, and /health SHA.

Install
npx skills add 'https://github.com/kentcdodds/kody/tree/main/.agents/skills/control-kody'
Download bundle ↓
main · 8beb6cdScanned 2026-09-15

Contributors

GitHub-linked commit authors for this SKILL.md at the saved revision. Co-authors and history before file renames are not included.

File history ↗
View on GitHub
---name: control-kodydescription: >  Drive and verify the Kody app with a Feature Map and one CLI. Use when  changing UI, account routes, preview deploys, or proving a Cloud Agent change  with a real origin, session, and /health SHA.--- # control-kody Do not invent a throwaway curl script, scrape PR comments by hand, or rediscoveraccount routes from `routes.ts`. Use the CLI and the Feature Map. ```bashnode tools/control-kody.ts doctornode tools/control-kody.ts devnode tools/control-kody.ts loginnode tools/control-kody.ts request GET /account/waiting.jsonnode tools/control-kody.ts map waitingnode tools/control-kody.ts health --sha <merge-sha>node tools/control-kody.ts preview -- --request 'GET /account/waiting.json' --check /account/waitingnode tools/control-kody.ts package-create --origin <preview> --package-name <leaf-or-@scope/leaf> [--head-ahead]``` `--kody-id` is an alias for `--package-name`.`npm run control-kody -- <command>` is the same entry. ## Feature Map [references/features/README.md](./references/features/README.md) is thehuman-readable index. `tools/control-kody/feature-catalog.ts` is themachine-readable source. `map --check` (and its node test) fail when a listedpath leaves `routes.ts` or a required HTML route has no entry. Load **one** feature file for the surface you are changing. ## Seed users - Local: `jane@example.com` / `ilikecode` (non-admin)- Preview: `me@kentcdodds.com` / `ilikecode` (non-admin, empty until you create  data through JSON APIs, or `package-create` for a saved package)- `/admin` 403 and `/mcp` 401 are expected for those seeds ## Proof CI green is not enough for a user-visible account change. Prefer: 1. `doctor` then `dev` or `preview`2. `request` / `--check` as the seed user **with data for this change**3. A computerUse video or screenshot of the same page4. After merge, `health --origin https://kody.codes --sha <merge>` (full SHA,   unique short SHA, or a later descendant HEAD that contains the merge) See[docs/contributing/control-kody.md](../../../docs/contributing/control-kody.md)and [preview-manual-test](../preview-manual-test/SKILL.md). 
Referenced from AGENTS.md

These references come from AGENTS.md at the skill snapshot.

AGENTS.md · same revision ↗
Source excerpt starting at line 28.
- [docs/contributing/control-kody.md](./docs/contributing/control-kody.md) and  the [control-kody skill](./.agents/skills/control-kody/SKILL.md)- Documentation principles (usage vs contributing, MCP text, gardening, prefer