docs-update

Update durable documentation after validated change.

9 stars

bymlucascosta

View on GitHub Installation ↓

Best use case

docs-update is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Update durable documentation after validated change.

Teams using docs-update should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/docs-update/SKILL.md --create-dirs "https://raw.githubusercontent.com/mlucascosta/ia_boilerplate/main/.agents/skills/docs-update/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/docs-update/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How docs-update Compares

Feature / Agent	docs-update	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Update durable documentation after validated change.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Purpose

Keep durable documentation aligned with real, verified behavior.

# Read First

- `.agents/AGENTS.md`
- `docs/ai/DECISION_RULES.md`

# Use When

- Durable knowledge changed
- The repo contract or workflow docs need adjustment

# Output

- Accurate documentation with no speculative claims

# Prohibitions

- Do not document behavior that has not been validated