cli-reference-drift
/cli-reference-drift
Check the website CLI reference (website/src/content/docs/reference.mdx) for drift against the actual dotsecenv CLI, and run it before cutting a release. Use when preparing a release, when asked to verify the CLI docs are in sync or check reference drift, or after adding or changing a command or flag. Triggers on: release, cli reference drift, reference out of date, docs in sync, before release, new command, new flag.
- Author
- dotsecenv ↗
- Repository
- dotsecenv ↗
- Licence
- Apache-2.0
- Last repository change
- 11.09.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 11.09.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: check.sh
What it does and when to use it
Check the website CLI reference (website/src/content/docs/reference.mdx) for drift against the actual dotsecenv CLI, and run it before cutting a release. Use when preparing a release, when asked to verify the CLI docs are in sync or check reference drift, or after adding or changing a command or flag. Triggers on: release, cli reference drift, reference out of date, docs in sync, before release, new command, new flag.
Original author description
Check the website CLI reference (website/src/content/docs/reference.mdx) for drift against the actual dotsecenv CLI, and run it before cutting a release. Use when preparing a release, when asked to verify the CLI docs are in sync or check reference drift, or after adding or changing a command or flag. Triggers on: release, cli reference drift, reference out of date, docs in sync, before release, new command, new flag.
How it works
- Run it
- What it reports
- Act on the report
- Release gate
SKILL.md preview
--- name: cli-reference-drift description: > Check the website CLI reference (website/src/content/docs/reference.mdx) for drift against the actual dotsecenv CLI, and run it before cutting a release. Use when preparing a release, when asked to verify the CLI docs are in sync or check reference drift, or after adding or changing a command or flag. Triggers on: release, cli reference drift, reference out of date, docs in sync, before release, new command, new flag. --- # CLI Reference Drift Check The website CLI reference at `website/src/content/docs/reference.mdx` is hand-curated (it carries examples, JSON output schemas, sample outputs, exit codes, and a config-file reference that cobra cannot generate). Because it is hand-written, it can drift from the actual CLI. Run this check before every release to catch commands or flags that exist in the binary but are missing from the page. ## Run it ```bash bash .agents/skills/cli-reference-drift/check.sh ``` The script runs the repo's `make docs` target to generate the live command and flag inventory from source (into `build/cli`), then compares it against `reference.mdx`. It exits non-zero when it finds drift. No network is needed (dependencies are vendored); a Go toolchain and `make` on `PATH` are required. ## What it reports - **MISSING command** — a CLI command with no matching `##`/`###` heading in `reference.mdx`. - **MISSING flag** — a command-specific (long) flag not mentioned anywhere in `reference.mdx`. - **DUPLICATE heading** — the same `##`/`###` heading text appears more than once (a copy-paste or stale-section bug). ## Act on the report For each genuine finding, edit `reference.mdx`: - Missing command or flag: add it in the page's existing style — a heading, a one-line description, an **Options** table, and at least one **Examples** block. Place it under the right parent section (e.g. a new `secret` subcommand goes under `## secret`). - Duplicate or stale heading: remove the redundant section. Re-run the check until it reports `no drift`. Known false positives to ignore: - `completion bash` / `zsh` / `fish` are documented under `## completion` as `### Bash` / `### Zsh` / `### Fish`, not as `### completion <shell>`. ## Release gate This is a pre-release step. Before running `rt git::release` (see [CLAUDE.md](../../CLAUDE.md) "Release new version"), run this check and resolve any drift. Do not release with an out-of-sync CLI reference. The page is the canonical CLI reference at <https://dotsecenv.com/reference/>; keeping it honest is the point of this check.
Files in this package (2)
- SKILL.md 3 KB
- check.sh 3 KB
Versions
The database has no other skills named cli-reference-drift.
Database snapshot: 13.11.2026 · package version 23a009bb9061 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100docs-sync
Audit and update Argus user-facing docs (README, docs/**/*.md, site/*.html) against the code truth. Detects version drift, command-count drift, i18n parity violations, and stale CLI examples. Use before a release, or any time the user asks to "sync docs", "update docs", "fix… - 100cli-commands
Use when adding or modifying CLI command (`but` commands) under `crates/but/src`. - 100repo-website-api-create
Create new API reference pages for the Valibot website at website/src/routes/api/. Use when adding documentation for new schemas, actions, methods, or types. Covers reading source code, creating properties.ts and index.mdx files, updating menu.md, and cross-referencing related APIs. - 100skillshare-update-docs
Update website docs to match recent code changes, cross-validating every flag against source. Use this skill whenever the user asks to: update documentation, sync docs with code, document a new flag or command, fix stale docs, or update the README. This skill covers all… - 90sync-docs-release
Use when the user wants to sync docs and then cut a release in one shot. Combines sync-docs (which lands its edits through its own docs PR) → optional merge of that PR → create-release in sequence. Triggers on phrases like "sync docs and release", "sync and cut a release",… - 100update-docs
This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change",…