readme-generator

Generates README.md files from analyzed repository structure and contents.

1|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/SSiertsema/claude-code-plugins --skill readme-generator-ssiertsema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: readme-generator
Source: https://github.com/SSiertsema/claude-code-plugins/tree/main/.claude/skills/readme-generator
Command: npx skills add https://github.com/SSiertsema/claude-code-plugins --skill readme-generator-ssiertsema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate accurate, comprehensive README.md files by analyzing a project's codebase, structure, and documentation, then validating findings with stakeholders. It also detects monorepos and can generate root READMEs plus per-package READMEs to reflect the actual architecture.

Core Features & Use Cases

  • Grounded analysis: derives README content strictly from repository structure, manifests, docs, and code.
  • Monorepo support: detects monorepos and can generate root README plus sub-package READMEs.
  • Interactive validation: prompts user for confirmation at key decisions to ensure accuracy and alignment with project reality.

Quick Start

Provide the project path or description, and I will generate a root README along with sub-package READMEs for monorepos.

Frequently Asked Questions about readme-generator

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

FAQPage Schema
How do I auto-generate a README.md from my codebase structure and contents?

Yes, monorepo README generation detects multi-package architectures and produces both a root README and optional per-package READMEs. It analyzes the repository structure to reflect the actual project architecture across all sub-packages.

How does interactive validation work during README generation?

Interactive validation prompts the user for confirmation at key decision points during README generation. This stepwise approval process ensures that all generated documentation accurately aligns with project reality before any files are written to disk.

What's the best way to ensure generated documentation matches my actual repository content?

The best way to ensure documentation matches your repository is to use a grounded analysis approach. This technique derives README content strictly from actual repository structure, manifests, docs, and code rather than generating generic or speculative descriptions.

Do I need to prepare any specific manifests or docs before generating a root README?

No special preparation is required beyond having your existing repository manifests, docs, and code accessible. The generator analyzes the available project structure and contents directly to produce a root README, requiring only the project path to begin.