Menu
Sync documentation with recently closed GitHub issues
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Reconstruct Dazzle/HM judgement from stems before inventing structure
Reconstruct Dazzle/HM judgement from stems before inventing structure
Run all quality checks on modified files — the on-demand pre-ship quality gate
Commit, verify, tag, and push with the repo's pre-flight gate suite (lint, type, drift gates, docs build)
Use when authoring or revising trial.toml scenarios for dazzle qa trial — puts an LLM in the shoes of a real business user evaluating a Dazzle app. Use when the user asks to "set up qa trials", "write a trial scenario", "evaluate this app as a user", or mentions qualitative/trial/business-user testing. Also use when a trial report is sparse or unhelpful — the scenario itself is usually the root cause.
Use when writing or editing Dazzle .dsl files — syntax rules, the mistakes agents actually make, and pointers to the drift-gated references. Complements (never replaces) CLAUDE.md's DSL Quick Reference.
| name | docs-update |
| description | Sync documentation with recently closed GitHub issues |
Sync documentation with recently closed GitHub issues using LLM-powered analysis. Follow these steps exactly:
Run dazzle docs update --dry-run --since "$ARGUMENTS" to scan closed GitHub issues and preview proposed documentation changes.
dazzle docs update --dry-run (defaults to issues closed since the latest release tag).gh not authenticated, no API key), report the error clearly and stop.Read the dry-run output carefully. For each proposed patch:
Report a brief summary: how many issues were scanned, how many are relevant, and what patches are proposed.
Ask the user whether to:
dazzle docs update --yes --since <same-since-value>dazzle docs update --yes --since <value> --target changelogRun the chosen command. After it completes:
git diff --stat to show what changed.git checkout -- <file> and explain what went wrong.Ask the user if they want to commit and push the documentation updates. If yes, use /ship.