Our review
This workflow guides the editing of guide chapters, ensuring structural changes propagate to all dependent files.
Strengths
- Systematically checks impact of title, template, and canonical term changes.
- Automates cross-references updates like README and 'Next:' links.
- Enforces consistent style (prescriptive voice, required sections, heading hierarchy).
- Includes final verification with the cross-reference-check skill.
Limitations
- Does not handle non-structural edits (minor fixes, rewordings).
- Relies on presence of '11-failure-modes.md' chapter for footer handling.
- Requires manual execution of cross-reference-check after changes.
Use this workflow before making any substantive edit to a file in the guide/ directory, especially when changing a title, template reference, or canonical term.
Do not use it for minor corrections (typos, style tweaks) that do not affect the guide's structure.
Security analysis
SafeThe skill outlines a workflow for editing guide chapters, ensuring consistency across files. It only instructs reading, searching, and updating markdown files, with no destructive or exfiltration actions. No risk.
No concerns found
Examples
I need to change the title of Chapter 3 from 'Old Title' to 'New Title'. Please follow the edit-chapter workflow.In chapter 5, I'm replacing the template path 'templates/old.md' with 'templates/new.md'. Run the edit-chapter workflow to ensure all dependencies are updated.I'm changing the canonical term 'five-tier context hierarchy' to 'four-tier context hierarchy' across the guide. Use edit-chapter to update all occurrences.name: edit-chapter description: 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.
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
API Documentation Generator
Documentation
Automatically generates OpenAPI/Swagger API documentation.
Technical Writer
Documentation
Writes clear technical documentation following top style guides.
Hono Documentation Search
Documentation
Use the hono CLI to search and view Hono framework documentation. It provides commands like hono search and hono docs to quickly find and browse documentation directly from the terminal. This is useful when developing with Hono and needing instant access to API references or guides.