document

Generate markdown documentation from git diffs against a base branch.

Updated Mar 9, 2026

Search Tags:#git #developer tools #code review #documentation #feature documentation #markdown generation

Ready to run

npx skills add https://github.com/justinpbarnett/claude --skill document-justinpbarnett

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: document
Source: https://github.com/justinpbarnett/claude/tree/main/skills/document
Command: npx skills add https://github.com/justinpbarnett/claude --skill document-justinpbarnett

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of clear, concise markdown documentation for implemented features directly from code changes, saving significant time and ensuring documentation stays up-to-date.

Core Features & Use Cases

Automated Documentation Generation: Creates markdown files in docs/ based on git diffs.
Specification Integration: Optionally references original feature specifications for context.
Use Case: After completing a new user authentication feature, use this Skill to automatically generate the docs/feature-user-auth.md file, detailing what was built, how it works, and how to use it, by analyzing the code commits.

Quick Start

Use the document skill to generate documentation for the current feature based on git diffs.

Frequently Asked Questions about document

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

FAQPage Schema

How do I generate markdown documentation from git diffs?▼

You can generate markdown feature documentation by analyzing git diffs against a base branch, which automatically creates markdown files in the `docs/` directory detailing what was built and how it works.

What is the best way to automate feature documentation for code changes?▼

Automating feature documentation uses git diff analysis to produce clear markdown files, ensuring documentation stays up-to-date by deriving feature names and implementation details directly from branch commits.

Can I reference original specifications when generating docs from git diffs?▼

Yes, you can optionally reference original feature specifications when generating markdown documentation from git diffs, providing additional context to accurately detail the built feature and its usage.

Does documentation generation work with feature branches to derive names?▼

Yes, documentation generation derives feature names directly from branch names and uses the git diffs against a base branch to create the corresponding markdown file in the `docs/` directory.

How do I include screenshots in generated feature documentation?▼

You can optionally include screenshots in generated feature documentation by adding image references, which the markdown generation process supports alongside the analyzed git diff information in the `docs/` directory output.