update-docs

Update project documentation based on user-provided instructions.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/hafidzlvm/opencode --skill update-docs-hafidzlvm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-docs
Source: https://github.com/hafidzlvm/opencode/tree/main/.dsh/skills/update-docs
Command: npx skills add https://github.com/hafidzlvm/opencode --skill update-docs-hafidzlvm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping documentation in sync with code changes is tedious and often skipped. This Skill streamlines the process of updating documentation files so docs stay accurate and current. ## Core Features & Use Cases - Documentation Updates: Applies user-specified changes to project documentation files. - Command-Based Invocation: Triggered as /update-docs with arguments describing what to update. - Use Case: After refactoring an API endpoint, invoke the skill with a note about the change so the corresponding README or docs pages are updated to match. ## Quick Start Run /update-docs with a short description of the change, such as updating the README to reflect the new configuration options.

Frequently Asked Questions about update-docs

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

FAQPage Schema
How do I update project documentation after a code change?▼

Invoke the /update-docs command and pass a description of what changed as arguments. The skill treats your text as instructions and applies the corresponding updates to the documentation.

What arguments does the update-docs command accept?▼

Any free-form text you provide after /update-docs is treated as arguments describing the update. Write a natural-language instruction explaining which documentation should change and why.

Can update-docs handle multiple documentation files?▼

The skill delegates to the underlying command definition, which operates on the documentation relevant to your instructions. Specify the files or sections you want updated in your arguments for best results.

When should I not use an automated documentation update?▼

Avoid it for large documentation restructures or when tone and editorial judgment matter, such as public-facing guides. Automated updates work best for targeted, factual changes tied to code modifications.