docs-update

Update README and docs files with JSDoc comments and link validation.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/cpa03/blueprintify --skill docs-update-cpa03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-update
Source: https://github.com/cpa03/blueprintify/tree/main/.opencode/skill/docs-update
Command: npx skills add https://github.com/cpa03/blueprintify --skill docs-update-cpa03

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation drift is common during feature releases and maintenance. This skill standardizes the process of updating user guides, API references, and developer notes to ensure consistency across the project.

Core Features & Use Cases

  • Identify scope of changes (User facing vs Dev facing) and determine affected docs.
  • Update README.md when setup or usage changes.
  • Update docs/*.md (e.g., features.md, api.md) to reflect latest changes.
  • Update JSDoc comments to new functions to improve maintainability.
  • Verify links and formatting to prevent broken references.

Quick Start

Update the documentation to reflect the latest changes across README and docs/*.md, and add JSDoc comments to new functions.

Frequently Asked Questions about docs-update

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

FAQPage Schema
How do I prevent documentation drift when releasing new software features?

To prevent documentation drift, you must synchronize changes across user guides, API references, and developer notes. This skill identifies the scope of user-facing versus dev-facing changes and updates relevant README and docs files to maintain consistency during maintenance cycles.

How do I update README and docs files to reflect code changes?

Updating README and docs files requires identifying affected documentation based on code changes. You update README.md for setup or usage modifications, modify docs/*.md files to reflect latest changes, and add JSDoc comments to new functions to improve maintainability.

What is the best way to add JSDoc comments and validate links in project docs?

Adding JSDoc comments and validating links ensures project docs remain accurate and maintainable. This skill enforces adding JSDoc to new functions and verifies links and formatting across README and docs/*.md to prevent broken references during feature releases.

Does this documentation update process work for both user-facing and dev-facing changes?

Yes, this documentation update process works for both user-facing and dev-facing changes. It identifies the scope of changes to determine affected docs, ensuring synchronized updates to user guides and developer notes across the entire software project.

Why does documentation become inconsistent during software maintenance cycles?

Documentation becomes inconsistent during software maintenance cycles because code changes outpace manual updates, causing drift. This skill standardizes the process of updating API references and developer notes to ensure consistency and prevent broken references.

Can I validate formatting and links across docs and README files automatically?

Validating formatting and links across docs and README files prevents broken references and maintains accuracy. This skill verifies links and formatting in documentation files to ensure consistent references after synchronized changes are applied.