stark-init-docs

Scaffold, backfill, migrate, and clean standardized developer documentation structures in git repositories.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/21StarkCom/stark-skills --skill stark-init-docs-21starkcom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stark-init-docs
Source: https://github.com/21StarkCom/stark-skills/tree/main/runtime-overrides/codex/skill/stark-init-docs
Command: npx skills add https://github.com/21StarkCom/stark-skills --skill stark-init-docs-21starkcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repositories often lack a consistent documentation structure, or have Markdown files scattered across random locations. This Skill sets up a standard docs layout (ADRs, specs, guides, references) and can generate content from git history or migrate existing docs into place. ## Core Features & Use Cases - Template scaffolding: Creates the standard docs directory tree, mkdocs.yml, PR template, CODEOWNERS, and doc-staleness config, all idempotently. - Backfill from history: Generates ADRs for major technology choices, stub specs from merged PRs, and setup/development/deployment guides by analyzing git log, GitHub PRs, and codebase config files. - Upgrade and clean modes: Migrates scattered Markdown files into the standard layout with link rewriting, or removes scaffold files while preserving user-generated content. - Use Case: After adopting a docs convention, run the upgrade and backfill modes together to migrate existing Markdown docs into docs/ and auto-generate ADRs and guides from repository history. ## Quick Start Ask the assistant to run stark-init-docs with the backfill mode to scaffold the docs structure and generate documentation from this repository's git history.

Frequently Asked Questions about stark-init-docs

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

FAQPage Schema
How do I scaffold a standard docs structure in a git repository?▼

Run the skill with the --template mode to create docs subdirectories (adr, specs, retros, guides, reference, architecture), mkdocs.yml, a PR template, CODEOWNERS, and a doc-staleness config. All operations are idempotent and existing files are skipped.

How to generate ADRs automatically from git history?▼

Use the --backfill mode, which analyzes git log, merged PRs, and dependency manifests to generate ADRs only for major technology choices like language, framework, and database. Each ADR is dated to the earliest commit introducing the technology.

Can I migrate existing Markdown docs into a standard layout?▼

Yes, the --upgrade mode classifies tracked Markdown files outside docs/ as spec, adr, guide, reference, or architecture, moves them with git mv, and rewrites internal links. Protected files like README, AGENTS.md, and generated or vendored content are never moved.

Does the backfill mode work without the GitHub CLI?▼

Yes. If the gh CLI is unavailable or fails, the skill warns that PR history could not be fetched and continues generating documentation from commits and codebase analysis alone.

Will the clean mode delete my handwritten documentation?▼

No. The --clean mode requires explicit confirmation and only removes scaffold files such as the ADR template, mkdocs.yml, and empty directories. User-generated content in docs/ and files with commits beyond the initial scaffold are preserved.