Create and maintain structured repository documentation with frontmatter and index regeneration.
npx skills add https://github.com/heliohq/ship --skill write-docs-heliohq
Please help me install this Agent Skill. Skill: write-docs Source: https://github.com/heliohq/ship/tree/main/skills/write-docs Command: npx skills add https://github.com/heliohq/ship --skill write-docs-heliohq
This Skill turns ad hoc documentation updates into a consistent, governed process for creating and maintaining structured docs under docs/ with clear ownership, lifecycle status, and discoverability.
Ask the AI to create or update a docs/ file that follows the frontmatter, numbering, status, and index regeneration rules in this Skill.
High-intent search queries and answers about installing and using this skill.
Maintain structured repository documentation by applying required frontmatter, numbering, lifecycle status, and cross-reference conventions to guides and references. This ensures docs remain current and governed through index regeneration and status validation.
The best way to regenerate a docs index is to apply category rules such as numbering, related links, and status lifecycle checks after revising existing documentation. This preserves cross-references and ensures accurate content discoverability.
Create new troubleshooting notes and design docs by following structured naming conventions and adding required frontmatter. This governs the documentation process by establishing clear ownership and lifecycle status from the start.
You can update existing docs safely by preserving status, cross-references, and last-modified tracking. Revising documentation this way prevents history loss while maintaining structural integrity across the knowledge base.
Documentation requires code-verified claims before marking content as current to ensure accuracy and prevent outdated information. Status validation enforces this lifecycle check, guaranteeing that current docs reflect verified repository behavior.
You need structured documentation governance when ad hoc updates cause inconsistent ownership, unclear lifecycle status, and poor discoverability. Applying frontmatter standards and index regeneration turns fragmented docs into a searchable knowledge base.
spencerbeggsAnalyze repository file structures to determine project type and technical metadata.
liangdabiaoDeploy Quartz v4 static sites from Markdown wikis to Cloudflare Pages, Vercel, or GitHub Pages.
VladlenFilimonovStandardize repository markdown documentation conventions and lifecycle management.
timequityValidate Rust fullstack project initialization with build, health, static, and HTMX checks.
