bootstrap

Append missing documentation sections to CLAUDE.md without overwriting existing content.

Updated Apr 1, 2026

Search Tags:#bootstrap #runbooks #architecture-docs #docs-automation #internal-docs #changelogs #post-mortems

Ready to run

npx skills add https://github.com/hpsgd/turtlestack --skill bootstrap-hpsgd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bootstrap
Source: https://github.com/hpsgd/turtlestack/tree/main/plugins/product/internal-docs-writer/skills/bootstrap
Command: npx skills add https://github.com/hpsgd/turtlestack --skill bootstrap-hpsgd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bootstrap internal documentation conventions and merge missing sections into CLAUDE.md to keep docs consistent.

Core Features & Use Cases

Appends architecture docs, runbooks, changelogs, and post-mortem templates to CLAUDE.md.
Idempotent merges: only missing sections are appended, existing content is preserved.
Supports onboarding new projects by establishing a consistent docs baseline.

Quick Start

Bootstrap the internal documentation conventions for your project by merging missing sections into docs/content/CLAUDE.md.

Frequently Asked Questions about bootstrap

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

FAQPage Schema

How do I bootstrap internal documentation conventions for a new software project?▼

To bootstrap internal docs, this Skill appends missing architecture docs, runbooks, changelogs, and post-mortem templates into a central CLAUDE.md file, establishing a consistent documentation baseline for your project.

How do I add architecture docs and runbooks to CLAUDE.md without overwriting existing content?▼

It uses an idempotent merge process to append missing sections like architecture docs and runbooks to CLAUDE.md, ensuring existing content is preserved without duplication across multiple runs.

What is the best way to standardize changelogs and post-mortems across multiple repositories?▼

Standardizing changelogs and post-mortems is achieved by applying a frontmatter-driven bootstrap process that creates or updates docs/content/CLAUDE.md, enforcing consistent baseline documentation conventions across repositories.

Can I use this to merge internal docs sections idempotently for project onboarding?▼

Yes, it supports onboarding new projects by establishing a consistent docs baseline, applying idempotent merges to append only missing sections without duplicating content in the target CLAUDE.md file.

Does bootstrapping internal docs require any external dependencies or components?▼

No external dependencies or components are required to bootstrap internal documentation conventions, as the Skill operates independently to merge missing sections into the CLAUDE.md file.

Why does my internal docs bootstrap create duplicate sections in CLAUDE.md?▼

Duplicate sections should not occur because the merge process is idempotent, only appending missing sections while preserving existing content to avoid duplication in CLAUDE.md.