doc-gen

Generate spec and retro documents from GitHub issues, PRs, and commits.

1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/becky3/ai-assistant --skill doc-gen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-gen
Source: https://github.com/becky3/ai-assistant/tree/main/.claude/skills/doc-gen
Command: npx skills add https://github.com/becky3/ai-assistant --skill doc-gen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of project documentation by harvesting information from Issues, PRs, and commit history and formatting it according to CLAUDE.md rules.

Core Features & Use Cases

  • Automated spec & retro generation: Produce specification documents and retrospectives from development activity.
  • Template-based output: Conforms to the CLAUDE.md style and project templates.
  • Use Case: When a feature is finished, generate a formal spec and a retrospective to capture lessons learned.

Quick Start

Run doc-gen with a type and feature name, for example: doc-gen spec login-flow

Frequently Asked Questions about doc-gen

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

FAQPage Schema
How do I generate documentation from GitHub issues and commit history?

You can generate documentation from GitHub issues and commit history by running an automated tool that harvests project activity and formats it into structured spec or retro documents using predefined CLAUDE.md templates.

What is the best way to automate spec generation for software features across repositories?

Automating spec generation across repositories requires harvesting pull requests and commit data, then formatting the output according to project templates to produce formal specification documents for completed features.

Do I need CLAUDE.md templates to produce specification and retrospective documents?

Yes, CLAUDE.md templates are required to produce specification and retrospective documents, as the automated generation process conforms to these predefined rules to structure the harvested GitHub activity data.

Can I use project activity from pull requests to create retrospective documents?

Yes, you can use project activity from pull requests to create retrospective documents by extracting development history and formatting it into structured retrospectives that capture lessons learned after a feature is finished.

What limitations exist when automating documentation from project activity across multiple repositories?

Limitations include requiring GitHub data access for project activity and preconfigured CLAUDE.md templates, meaning the automation cannot produce structured spec or retro outputs without these environment prerequisites in place.