gendoc-rebuild-templates

Regenerate templates under templates/ to satisfy Iron Rules.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/ibalasite/gendoc --skill gendoc-rebuild-templates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gendoc-rebuild-templates
Source: https://github.com/ibalasite/gendoc/tree/main/skills/gendoc-rebuild-templates
Command: npx skills add https://github.com/ibalasite/gendoc --skill gendoc-rebuild-templates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rebuilds all template files under templates/ including *.review.md and *.gen.md to enforce iron rules and keep upstream mappings current.

Core Features & Use Cases

  • Regenerates both review and gen templates across all types, ensuring structural integrity and alignment with the upstream docs.
  • Validates and applies the cumulative upstream reading rules, keeping IDEA Appendix C handling in mind.
  • Ideal for adding new file types or updating the templates pipeline; triggers a fresh, consistent template baseline.

Quick Start

Run the gendoc-rebuild-templates skill to rebuild all template files and verify upstream alignment.

Frequently Asked Questions about gendoc-rebuild-templates

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

FAQPage Schema
How do I regenerate documentation templates and enforce consistent structure across a repository?

To regenerate documentation templates, this Skill scans existing files under templates/ and rebuilds all *.review.md and *.gen.md files in one pass. It enforces defined Iron Rules to maintain structural integrity and consistent quality across all document types.

How does validating upstream documentation mappings work during template generation?

Validating upstream documentation mappings works by applying a Step 0–4 workflow that scans existing templates and checks upstream alignments. It ensures regenerated docs correctly reference upstream sources while handling IDEA Appendix C rules cumulatively.

When do I need to rebuild all gen and review markdown templates in my project?

You need to rebuild gen and review markdown templates when adding new file types or updating the templates pipeline. Running a full rebuild triggers a fresh, consistent template baseline that aligns all documents with current upstream sources.

What is the best way to update multiple documentation templates without manual editing?

The best way to update multiple documentation templates without manual editing is running an automated rebuild pass. This Skill requires no additional inputs beyond the repository state and follows the official templates upgrade process to regenerate all files.

Do I need any dependencies or external components to run a full template rebuild?

No, you do not need any dependencies or external components to run a full template rebuild. The Skill operates solely on the repository state, requiring no additional inputs to scan templates, validate upstreams, and regenerate documentation.

Why does my documentation template structure become inconsistent when adding new file types?

Documentation template structure becomes inconsistent when new file types bypass the official upgrade process. Rebuilding all templates enforces Iron Rules and validates upstream mappings, ensuring structural alignment and quality across both review and gen document types.