docs-update-check

name

docs-update-check

description

Use after implementing features, changing configuration, modifying CLI commands, updating router behavior, altering architecture, or making any user-facing changes. Triggers a documentation review to check if docs-website/ needs updating. Use this skill whenever you finish writing code that changes how users interact with the platform — new flags, config options, API changes, new UI features, behavioral changes, deprecations, or new components. Even small changes like adding an environment variable or a new CLI flag need doc coverage.

Documentation Update Check

After making code changes that affect user-facing behavior, check whether the documentation in docs-website/ needs to be updated. Outdated or missing documentation is one of the most common sources of user frustration — users read the docs expecting them to match reality, and when they don't, trust erodes. This skill ensures documentation stays in sync with code.

When This Applies

This check applies when changes touch any of these areas:

• New features or capabilities — anything users can now do that they couldn't before
• Configuration changes — new options, renamed keys, changed defaults, removed options
• CLI command changes — new commands, new flags, changed behavior, new output formats
• Router behavior — new middleware, changed request handling, new directives, subscription changes
• Studio UI — new pages, new settings panels, changed workflows
• API changes — new endpoints, changed request/response shapes, new auth methods
• Architecture changes — new components, changed data flow, new deployment requirements
• Deprecations or removals — anything users relied on that is going away
• Environment variables — new ones, changed names, changed defaults