edit-chapter
Safe edit handler for guide chapters. Maintains structure and updates related documentation automatically.
Install
mkdir -p .claude/skills/edit-chapter && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13221" && unzip -o skill.zip -d .claude/skills/edit-chapter && rm skill.zipInstalls to .claude/skills/edit-chapter
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Invoke this skill before making substantive edits to any file in guide/ — changing content, titles, template references, or canonical terms. Follow this workflow proactively when editing chapters, not only when the user explicitly requests it. Ensures structural changes propagate to all dependent files.Key capabilities
- →Update README.md chapter listings
- →Modify CLAUDE.md references
- →Adjust 'Next:' links in chapter footers
- →Verify template paths in `templates/`
- →Search and update canonical terms across `.md` files
- →Run cross-reference checks for consistency
How it works
This skill provides a guided workflow to ensure structural changes in guide chapters propagate to all dependent files. It checks for changes in H1 titles, template references, and canonical terms.
Inputs & outputs
When to use edit-chapter
- →Updating a guide chapter title
- →Renaming a template path
- →Changing a canonical project term
- →Adding a new guide chapter
About this skill
Edit Chapter
Guided workflow for safely editing a guide chapter. Ensures structural changes propagate to all dependent files.
Before Editing
- Read the entire chapter file
- Note the current H1 title (line 1)
- Note any template paths referenced (lines mentioning
templates/) - Note any canonical terms used ("five-tier context hierarchy", "document cascade")
During Editing
- Maintain prescriptive voice — no hedging phrases (see
.claude/rules/guide-chapter.md) - Preserve required sections: Principles, What the Human Should Do, What the Agent Should Do
- Use RecipeVault for examples (not "Beacon")
- Keep heading hierarchy:
##for major sections,###for subsections - Use fenced code blocks with language identifiers
After Editing
Check each condition and take action if true:
If the H1 title changed:
- Update
README.mdchapter listing (lines 45-93) - Update
CLAUDE.mdif the chapter is referenced there - Update the "Next:" link in the prior chapter's footer
If template references changed:
- Verify each referenced template path exists in
templates/ - If a path was removed or renamed, grep for the old path across the repo
If a canonical term changed:
- Search all
.mdfiles for the old term - Update every occurrence to match the new term
Always (every edit):
- Verify the chapter ends with a
Next:footer linking to the correct successor chapter, unless the file is11-failure-modes.md - The footer must follow this format:
--- Next: [Chapter NN -- Title](NN-slug.md)
If any structural change was made (title, file references, canonical terms):
- Run the
cross-reference-checkskill to verify consistency
When not to use it
- →When making minor content edits that do not affect structure
- →When editing files outside the `guide/` directory
- →When the user explicitly requests a different workflow
Limitations
- →The skill is specifically for files within the `guide/` directory
- →The skill requires explicit checks and actions after editing
- →The skill does not automatically rewrite content
How it compares
This skill automates the propagation of structural changes across multiple files, preventing manual errors and ensuring consistency, unlike a manual update process.
Compared to similar skills
edit-chapter side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| edit-chapter (this skill) | 0 | 4mo | No flags | Intermediate |
| ml-paper-writing | 48 | 6mo | Review | Advanced |
| docs-review | 10 | 7mo | No flags | Beginner |
| claude-md-improver | 21 | 6mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
ml-paper-writing
davila7
Write publication-ready ML/AI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Use when drafting papers from research repos, structuring arguments, verifying citations, or preparing camera-ready submissions. Includes LaTeX templates, reviewer guidelines, and citation verification workflows.
docs-review
metabase
Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.
claude-md-improver
anthropics
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project memory optimization".
write-docs
tldraw
Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing guidance is needed. Applies to docs in apps/docs/content/.
update-docs
vercel
This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.
wiki-architect
microsoft
Analyzes code repositories and generates hierarchical documentation structures with onboarding guides. Use when the user wants to create a wiki, generate documentation, map a codebase structure, or understand a project's architecture at a high level.