edit-chapter

Propagate chapter title and template edits across README.md, CLAUDE.md, and navigation files.

2|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/brandonavant/harness-engineering-guide --skill edit-chapter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edit-chapter
Source: https://github.com/brandonavant/harness-engineering-guide/tree/main/.claude/skills/edit-chapter
Command: npx skills add https://github.com/brandonavant/harness-engineering-guide --skill edit-chapter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Editing a chapter can ripple across multiple files. This Skill provides a safe, repeatable workflow to propagate every structural change.

Core Features & Use Cases

  • Enforces preservation of required sections (Principles, What the Human Should Do, What the Agent Should Do) and maintained heading structure when edits occur.
  • Updates dependent files (README.md chapter listings, CLAUDE.md references, and Next: footer links) to maintain consistency after changes.
  • Triggers a cross-reference check after any structural modification to ensure the guide remains coherent.

Quick Start

Review the current chapter and apply the safe-edit workflow to propagate structural changes across all dependent files.

Frequently Asked Questions about edit-chapter

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

FAQPage Schema
How do I propagate markdown chapter edits across multiple documentation files?

Propagate markdown chapter edits by applying a safe-edit workflow that updates dependent files like README.md and CLAUDE.md, ensuring structural consistency across the guide. It triggers cross-reference checks after modifying chapter titles or templates.

How do I maintain cross-references in documentation when modifying chapter titles?

Maintain cross-references by enforcing automatic update actions that verify guide coherence after structural changes occur. The workflow checks navigation links and dependent file references whenever you modify chapter titles or canonical terms.

Can I preserve required sections and heading structure when editing guide chapters?

Yes, you can preserve required sections such as Principles, What the Human Should Do, and What the Agent Should Do. The safe-edit workflow enforces preservation of maintained heading structure whenever chapter edits are applied.

What is the best way to update Next footer links and navigation after structural changes?

Update Next footer links and navigation by triggering a cross-reference check after structural modifications. This workflow automatically updates dependent navigation files to maintain consistency across README.md and CLAUDE.md references.

How do I keep canonical terms consistent across README.md and CLAUDE.md files?

Keep canonical terms consistent by applying the chapter edit propagation workflow, which automatically updates dependent files. It ensures that term modifications ripple safely across all cross-referenced documentation files.

When should I use a safe-edit workflow for documentation propagation?

Use a safe-edit workflow for documentation propagation when edits modify chapter titles, templates, or canonical terms. It provides a repeatable process to update dependent files and enforce cross-reference checks for structural changes.