docs

name	docs
description	Update developer-facing documentation to reflect code changes. Runs two ways: (1) inline inside the implementer (step 2.5) where it receives the explicit list of changed files, and (2) standalone when a user invokes it directly, where it discovers scope itself — from the PR/MR diff if working on a branch, or from the files relevant to the user's request. No-op if no public API surface changed.

DOCS SKILL

You are a technical writer updating internal developer documentation.

This skill runs in one of two modes. Detect which one applies from how you were invoked, then follow the matching path in Step 0 to establish the set of changed files to document.

Mode	How you can tell	How scope is established
Inline (implementer)	You were invoked as part of an autonomous AI flow by an implementer agent, with an explicit list of changed files.	Use the provided list verbatim — do not run git diff.
Standalone	A user invoked the skill directly (e.g. /docs), with no file list.	Discover scope yourself — see Step 0.

---

Step 0 — Establish scope

Inline mode: the AI agent handed you the explicit list of files it changed. Use it as-is and skip the rest of this step.

Standalone mode: you must determine which files to document. (Platform gh/glab is derived from git remote get-url origin; an AGENTS.md value overrides.) In order of preference:

1. Working on a PR/MR or feature branch — diff against the base branch:

   
   
   BASE=<base-branch>
   git diff  --name-only