Skip to content

modem-dev/ossrules / public/files/kody/.agents/skills/control-kody

control-kody

Unverified

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 rediscover account routes from routes.ts. Use the CLI and the Feature Map.

node tools/control-kody.ts doctor
node tools/control-kody.ts dev
node tools/control-kody.ts login
node tools/control-kody.ts request GET /account/waiting.json
node tools/control-kody.ts map waiting
node tools/control-kody.ts health --sha <merge-sha>
node tools/control-kody.ts preview -- --request 'GET /account/waiting.json' --check /account/waiting
node 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 is the human-readable index. tools/control-kody/feature-catalog.ts is the machine-readable source. map --check (and its node test) fail when a listed path 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 page
  4. 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 and preview-manual-test.

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 318kUpdated Claude CodeCodexUnverifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 117kUpdated Claude CodeCodexUnverifiedInstall