Menu
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.
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 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.
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.
| name | onboard-dir |
| description | 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. |
The drift gate (tools/check-drift.sh) now hard-fails on any projects/*/ dir that is in neither .gitmodules nor _data/projects.yml. This skill resolves it.
ls projects/<name>; git -C projects/<name> remote -v; git -C projects/<name> log -1
git submodule add -b <branch> <remote-url> projects/<name>
_data/projects.yml (or run /register-project): submodule_path: projects/<name>, correct branch, category, status, and a tier/license if not derivable.tools/dash-gen readme (refresh the README AUTO span).tools/dash audit <name> (check it against its tier baseline).tools/check-drift.sh (confirm parity is restored).Confirm there's no uncommitted or unpushed work first:
git -C projects/<name> status --short && git -C projects/<name> log --oneline @{u}..HEAD
rm -rf projects/<name>
The dir's own remote repo (if any) is untouched.
Never rm -rf a dir with uncommitted or unpushed commits without surfacing it and asking. If it has a .git and a remote, default to onboarding, not deleting.