document

Update READMEs, API docs, and changelogs from code diffs.

10|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/fiftynotai/igris-ai --skill document-fiftynotai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document
Source: https://github.com/fiftynotai/igris-ai/tree/main/.claude/skills/document
Command: npx skills add https://github.com/fiftynotai/igris-ai --skill document-fiftynotai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keep project documentation (README, API docs, architecture notes, inline comments, migration guides, and changelogs) accurate, consistent, and aligned with code changes so users and engineers can rely on up-to-date guidance.

Core Features & Use Cases

  • README updates: Refresh feature summaries, installation steps, and examples after changes.
  • API documentation: Document public interfaces, parameters, return values, and usage examples.
  • Architecture and migration guides: Capture design decisions, upgrade paths, and breaking changes.
  • Use Case: After merging a feature that adds a new public API, update the README and API reference with usage examples and a changelog entry, and validate code samples and links.

Quick Start

Ask the document skill to update the README and API docs to reflect the latest commit by summarizing the changes and adding runnable examples.

Frequently Asked Questions about document

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

FAQPage Schema
How do I update README and API documentation after merging new code changes?

Update README and API documentation by reading existing docs and code diffs to generate clear updates, runnable examples, and changelog entries. This ensures your project documentation accurately reflects the latest public interfaces and feature summaries.

What is the best way to automate architecture docs and migration guides for new releases?

Automate architecture docs and migration guides by capturing design decisions, upgrade paths, and breaking changes from code diffs. This documentation automation keeps your architecture notes accurate and aligned with new releases without introducing source modifications or TODO placeholders.

How do I validate code samples and links inside my API documentation?

Validate code samples and links inside API documentation by reading existing docs and diffs to ensure accuracy. The validation process checks that runnable examples work correctly and that no broken links or TODO placeholders remain in your updated documentation.

Can I generate changelog entries and migration guides without modifying my source code?

Yes, you can generate changelog entries and migration guides without modifying source code. The documentation update process ensures no source modifications or TODO placeholders are introduced, keeping your project docs accurate while leaving the actual codebase untouched.

When do I need to update API references and architecture notes for a project?

You need to update API references and architecture notes when code changes introduce new public APIs, architecture decisions, migrations, or releases. Keeping documentation accurate at these points ensures users and engineers can rely on up-to-date guidance.