anvil-boot

Bootstraps a project for the anvil toolkit by configuring CLAUDE.md, rules, docs, and hooks.

1|Updated Aug 27, 2026
One-click install
npx skills add https://github.com/rogerznts/anvil --skill anvil-boot-rogerznts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: anvil-boot
Source: https://github.com/rogerznts/anvil/tree/main/anvil/.claude/skills/anvil-boot
Command: npx skills add https://github.com/rogerznts/anvil --skill anvil-boot-rogerznts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a project to work with the anvil skill toolkit requires many coordinated steps: injecting directives into CLAUDE.md, creating project rules, scaffolding documentation, configuring the issue tracker profile, and installing a merge guard hook. Doing this manually is error-prone and inconsistent. This Skill runs the entire bootstrap as an idempotent, approval-gated workflow. ## Core Features & Use Cases - CLAUDE.md directive injection: Writes a delimited ANVIL:DIRECTIVES block into CLAUDE.md without touching existing project instructions, and migrates legacy mosk blocks. - Project rules generation: Scans the codebase and proposes .claude/rules/ files (project.md, anvil.md, frontend.md) with evidence-backed suggestions that require user approval. - Docs and tracker setup: Delegates to anvil-docs for docs/ scaffolding or adoption, and to anvil-setup to write the issue tracker profile that other skills read. - Merge guard and gitignore management: Installs and verifies the guard-spec-merge.sh hook, reconciles the anvil.lock manifest, and generates a per-skill .gitignore block. - Use Case: After installing anvil via degit into an existing repository, run the boot once to migrate from mosk, configure rules for a Payload CMS stack, and activate the spec merge guard. ## Quick Start Run the anvil-boot skill to prepare this project for the anvil toolkit and approve each proposed change as it is presented.

Frequently Asked Questions about anvil-boot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up the anvil toolkit in an existing project?▼

Install the payload with npx degit rogerznts/anvil/anvil . --force, then run the anvil-boot skill once. It injects directives into CLAUDE.md, proposes rules, sets up docs and the issue tracker profile, and installs the merge guard hook, asking for approval before each write.

How do I migrate from mosk to anvil?▼

The boot detects .claude/mosk/ or mosk-*.md agent files and presents a migration plan before deleting anything. It removes mosk personas, core files, and wrappers, converts the MOSK:DIRECTIVES block in CLAUDE.md to ANVIL:DIRECTIVES, and leaves your rules, docs, and settings untouched.

Is it safe to run anvil-boot more than once?▼

Yes, every step is idempotent and nothing is overwritten without warning. Only the delimited CLAUDE.md block and the empty docs tree are written without approval; rules, tracker profile, stack rules, and hooks are all proposed and wait for confirmation.

Does anvil-boot overwrite my existing CLAUDE.md or settings.json?▼

No. CLAUDE.md content outside the ANVIL:DIRECTIVES markers is never modified, and the merge guard hook is merged into .claude/settings.json rather than replacing it. Existing project hooks and instructions remain intact.

What is the anvil.lock file used for?▼

The anvil.lock lists which skills and agents the toolkit installed, letting anvil-update detect orphans and generating the .gitignore block. The boot verifies the lock against the disk and asks which entries are user-written before rewriting it.

Why does the boot install a git hook for spec merges?▼

The guard-spec-merge.sh hook blocks merging a spec branch while its ticket is open or the spec is not archived. The boot installs it as a PreToolUse hook and verifies it fires correctly, since an unverified check provides no protection.