Docs

Keep your project up to date

A project created from a kit records in kits.lock which kit it came from, what you chose and which files the kit wrote. Commit it: with it, the project gets the kit's improvements without losing your changes.

Update to the new kit

$ npx create-first-commit update --dry-run

Shows what would change; without --dry-run it applies it after you confirm. An update:

Adds the kit's new dependencies, skills, MCP servers and variables.
Rewrites the kit's section in AGENTS.md (the rest of the file is yours and is left alone).
Updates the kit's files you haven't modified. The ones you edited or deleted are listed and left alone.
Never uninstalls anything or reruns setup commands: whatever the kit stops using is listed so you decide.

To move to a specific version: npx create-first-commit update 1.2.0. Once a day, the CLI lets you know when there's a new version of your project's kit.

Add pieces from the catalog

$ npx create-first-commit add sentry

Picks the variant for your framework (Sentry for Next.js, Expo or Node), installs what's missing, and writes its config, its skill and its rule in AGENTS.md with its first steps. It checks requirements (Kokonut UI needs shadcn/ui) and also works in projects that weren't created from a kit. It accepts skills too: npx create-first-commit add owner/repo@skill.

Check the project

$ npx create-first-commit doctor

components: Another component library installed besides the chosen one (error: it breaks the AGENTS.md rule).
animation: Animation libraries that weren't chosen.
env: Variables from .env.example that are undefined or empty in .env / .env.local.
skills: Kit skills missing for one of your agents, with the command to install them.
files: Kit files that were deleted.
version: Whether there's a new version of the kit.

With --json it prints machine-readable output and exits with code 1 when there are errors: use it in CI or in a pre-commit hook.