auto-documentation

Analyze Git diffs to update living feature documentation under docs/afyapowers.

9|2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/iclinic/afyapowers --skill auto-documentation-iclinic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-documentation
Source: https://github.com/iclinic/afyapowers/tree/main/src/skills/auto-documentation
Command: npx skills add https://github.com/iclinic/afyapowers --skill auto-documentation-iclinic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically document features by analyzing code changes and updating living documentation in docs/afyapowers, ensuring docs stay in sync with implementation.

Core Features & Use Cases

  • Auto-detects code changes in a feature and updates the corresponding living documentation.
  • Matches changes to existing feature docs, and creates new docs when no match exists, preserving history with a changelog.
  • Integrates with the afyapowers workflow to keep docs up-to-date across all features.

Quick Start

Run the auto-documentation update after you implement a feature to refresh its docs.

Frequently Asked Questions about auto-documentation

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

FAQPage Schema
How do I automatically generate documentation from git diffs?

Automatically generate documentation from git diffs by analyzing code changes, mapping them to affected domains, and creating or updating living feature docs under your repository's docs directory while preserving historical changelog entries.

What are living feature docs and how do they stay in sync with code changes?

Living feature docs are documentation files that automatically reflect code changes. They stay in sync by detecting git diffs, matching changes to existing documents, and updating the content to ensure docs remain aligned with the implementation.

How do I update existing feature documentation without losing the changelog history?

Update existing feature documentation without losing changelog history by matching git diffs to current docs, modifying the matched files, and preserving all historical changelog entries within the repository's docs structure.

Does auto-documentation work across all features in a repository?

Auto-documentation operates across the entire repository to identify affected domains, automatically matching code changes to existing feature docs or creating new documents when no match exists to keep all features up-to-date.

When should I run documentation generation for my feature updates?

Run documentation generation immediately after you implement a feature to refresh its docs, ensuring the living documentation captures the latest code changes and maps them accurately to the corresponding feature docs.

What is the best way to keep documentation up-to-date with implementation changes?

The best way to keep documentation up-to-date with implementation changes is to auto-detect code modifications via git diffs, map them to feature docs, and create new documents when no match exists while preserving the changelog history.