doc-maintainer

Synchronize README, architecture, API, and requirements docs with code changes.

7|5|Updated Jun 2, 2023
One-click install
npx skills add https://github.com/sjmyuan/prompts --skill doc-maintainer-sjmyuan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-maintainer
Source: https://github.com/sjmyuan/prompts/tree/main/skills/doc-maintainer
Command: npx skills add https://github.com/sjmyuan/prompts --skill doc-maintainer-sjmyuan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that your project's documentation accurately reflects its current code, preventing outdated information and improving developer onboarding and user understanding.

Core Features & Use Cases

  • Impact Assessment: Automatically identifies which documentation sections need updates based on code changes (bug fixes, features, refactors).
  • Systematic Updates: Guides you through a structured process for making focused, accurate edits to requirements, architecture docs, READMEs, API docs, and more.
  • Use Case: After implementing a new feature, use this Skill to ensure the README, API documentation, and usage examples are all updated to reflect the new functionality.

Quick Start

Use the doc-maintainer skill to synchronize documentation after a code refactor.

Frequently Asked Questions about doc-maintainer

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

FAQPage Schema
How do I synchronize documentation with code changes after a refactor?

To synchronize documentation with code changes, you can assess the impact of bug fixes, features, and refactors to systematically update README, architecture, and API docs. This process ensures your technical writing accurately reflects the current codebase.

What is the best way to update API docs and READMEs for new features?

The best way to update API docs and READMEs for new features is to follow a structured validation checklist that provides focused edits and usage examples. This ensures developer guides accurately reflect the new functionality.

How does documentation impact assessment work for technical writing?

Documentation impact assessment works by automatically identifying which sections of your requirements, architecture docs, and API docs need updates based on specific code changes. It then guides you through making accurate, focused edits.

Can I generate migration guides for bug fixes and refactors?

Yes, you can generate migration guides and usage examples for bug fixes, features, and refactors. The documentation update process specifically provides these guides to help developers handle code modifications accurately.

Do I need specific documentation types to maintain code sync?

Yes, maintaining code sync requires adherence to specific documentation types such as README, architecture docs, API docs, and requirements. The process uses a validation checklist to ensure updates meet the required standards.

Why does keeping developer guides in sync with code prevent outdated information?

Keeping developer guides in sync with code prevents outdated information by systematically aligning requirements and API docs with current code changes. This structured update process improves developer onboarding and user understanding.