Menu
Run the dash drift gate and explain every failure in plain language with the exact fix. Use when CI drift-check fails or before opening a PR.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Deep-analyze a GitHub issue into a client-engagement estimate — classify scope, refine the plan (approach/deliverables/acceptance), and record an agent-refined estimate in _data/engagements.yml. Use when asked to "estimate", "quote", "scope", or "price" an issue or a repo's backlog, or to review/refine a draft the estimator produced.
Read the Monitor board health data, explain why each repo needs attention, and propose the next concrete action per repo. Use to turn monitoring signals into action, or as the input step of the self-evolution loop.
Read the committed Actions analytics (_data/actions_usage.yml), explain the worst workflows (cost, effectiveness, waste), and drive the next action — dispatch the actions-review issue-filer or fix a workflow directly. Use when asked "where are Actions minutes going" or after the daily actions-usage refresh.
Run a focused improvement pass on a single project (code quality, docs, tests, error handling) using the matching .github/agents persona. Use when a repo needs maintenance attention or as the action step of the evolution loop.
Scaffold a new project and register it in the dash. Use when starting a new repo/app that should appear in the portfolio.
Adopt (or remove) a project directory that exists on disk under projects/ but is in neither .gitmodules nor the registry. Use when the drift gate flags a stray/unregistered project dir.
| name | drift-report |
| description | Run the dash drift gate and explain every failure in plain language with the exact fix. Use when CI drift-check fails or before opening a PR. |
tools/check-drift.sh --report (never fails) to list all drift. Add --remote (or --ci) for the GitHub-reality check (g); --links needs a locally built _site + lychee._data/projects.yml or .gitmodules; run the update-registry skill. A stray/unregistered projects/* dir also fails (a) → route to the onboard-dir skill (adopt it or remove it).tools/dash-gen readme.--links only; advisory) → fix the pages lychee names, or rebuild _site.README.md.git -C <sub> checkout <declared-branch> (verify no in-progress work first; some submodules sit on feature branches intentionally).standardize-audit skill (tools/dash audit for the per-repo matrix).--remote/--ci only; advisory) — repo renamed/deleted on GitHub, or declared branch ≠ GitHub default → route to the update-registry skill to reconcile repo_url/.gitmodules/branch.python3 tools/schema_lint.py check . and fix what it names; stale generated projects/SCHEMA.md: run python3 tools/gen-projects-schema.py (never hand-edit it).Do not force-checkout a submodule that has uncommitted or unpushed work — surface it and ask first.