القائمة
Triage an incoming issue or external PR — verify the claim, then write a behavioral agent brief or record the rejection in the out-of-scope KB.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Cut an npm release of @kvnwolf/dobby from the main checkout — inferred bump, raw-TS tarball gate, publish, tag, GitHub release with changelog.
Syncs documentation, authors the commit message + PR body, runs the gate and performs the git/gh ceremony directly (stage → `dobby check --fix` → commit → push → PR), then monitors the PR to a verdict. Use when committing code, finishing a task, pushing changes, or creating a PR.
One-pass migration of a consumer repo off vite-plus onto @kvnwolf/dobby — swap deps, thin `tsconfig.json` and delete the now-default tool configs (biome/vite/vitest/drizzle, kept only for real deltas), move files to canonical paths, regenerate dobby.config.json, drop .conductor, rewire CI + Vercel build, verify with `dobby check`. Run in a consumer repo, once, after updating the dobby plugin.
Set up a repo (greenfield or existing) for the work skills — interview, install @kvnwolf/dobby, scaffold the base files + thin tsconfig, write the dobby.config.json contract. Run once.
Disciplined diagnosis loop for hard bugs — build a fast deterministic feedback loop, rank falsifiable hypotheses, instrument one variable at a time. Use when something is failing, a bug is intermittent or non-obvious, or there's a performance regression.
Dispatch a scoped, ad-hoc task to a worker agent (or a few in parallel) and review what comes back — without the full /dobby:execute plan-and-waves ceremony. Use for a small fix or change, or a bounded investigation, when you don't need a STATE.md spec.
| name | triage |
| description | Triage an incoming issue or external PR — verify the claim, then write a behavioral agent brief or record the rejection in the out-of-scope KB. |
| argument-hint | [issue/PR number or what to triage] |
| disable-model-invocation | true |
| allowed-tools | Bash(gh *), Bash(git *) |
You are the coordinator/architect. You run the tracker/PR mechanics (gh/git) yourself, read for synthesis, and delegate the doing — verification goes to a dobby:researcher, and any resulting build work is a downstream /dobby:scope goal, never inline edits by you. Take an incoming issue or external PR from "reported" to a decision the maintainer signs off on, backed by a durable brief or an out-of-scope record.
Scope of this skill (portable half): verify-the-claim, the behavioral agent brief, and the out-of-scope KB. The tracker is always the gh-authenticated repo, but building out a full role/state-machine — canonical role names, discovery queries, elaborate label transitions — is out of scope here. Triage what the maintainer points you at; don't invent a labeling machine.
Triage vs. address-review. This skill triages incoming requests — an issue or an external PR proposing a change. Review-bot / reviewer comments on your own open PR (Greptile, CodeRabbit, humans) belong to /dobby:address-review — if the user hands you review threads on their active PR, point them there.
gh mechanics. For every GitHub read/write (fetch an issue/PR, read comments, post a comment, checkout a PR branch) reuse the recipes in ../address-review/references/github-api.md — derive OWNER/REPO from gh repo view --json owner,name, nothing hardcoded. Don't re-author gh commands.
AI disclaimer. Every comment you post to the tracker during triage MUST start with this line:
> *This was generated by AI during triage.*
Read the full issue or PR — body, comments, author, dates; for a PR, the diff too (gh pr diff N, per ../address-review/references/github-api.md). Then run two checks against the codebase, reading for synthesis (explore with the project's domain glossary in CONTEXT.md, respect ADRs in the area):
docs/out-of-scope/*.md and surface any concept that resembles this request (match by concept, not keyword — "night theme" matches dark-mode.md). If one matches, tell the maintainer: "This resembles docs/out-of-scope/dark-mode.md — rejected before because [reason]. Still holds?"Both checks may also scan the tracker's open issues (is this concept already filed or previously rejected there?); that scan reads the configured tracker — read the tracker key from dobby.config.json narratively (absent → github) and follow the dedup / search recipe in ../backlog/references/trackers.md.
Present a short recommendation (bug vs enhancement, and your leaning) plus the codebase summary, including whether it's already implemented. Wait for the maintainer's direction before verifying or briefing.
dobby:researcherBefore any brief, confirm the claim actually holds. Delegate this to a dobby:researcher (Agent tool, subagent_type: "dobby:researcher") — the architect does not run repros itself. Task it to:
gh pr checkout N, per the github-api reference) and run the tests/commands the diff claims to satisfy. Confirm the diff does what it says.The researcher returns one of three verdicts:
| Verdict | Meaning | Effect on the brief |
|---|---|---|
| confirmed | Reproduced / the diff's tests pass | Strongest brief — fold the confirmed code path into it |
| failed | Could not reproduce / the diff's claim doesn't hold | Not a bug as reported (or the PR is broken) — tell the maintainer before briefing |
| insufficient | Not enough detail to attempt it | A strong signal to go back to the reporter for specifics before briefing |
Report the verdict to the maintainer and let them steer the outcome.
If the maintainer wants this actioned by an agent or a human, write a behavioral, not procedural brief following references/agent-brief.md. The brief is the contract; the original discussion is only context.
The one hard rule: describe interfaces and behavioral contracts — never file paths or line numbers. The brief may sit unactioned for weeks while the codebase moves; paths and line numbers go stale, interface descriptions don't. Sections: Category · Summary · Current behavior · Desired behavior · Key interfaces · Acceptance criteria (checkboxes, each independently verifiable) · Out of scope.
/dobby:scope as a goal to start a work session.When the maintainer decides not to action a request:
docs/out-of-scope/ — that KB is for rejected requests only; recording a built feature there poisons the dedup checks with a false rejection.../backlog/references/trackers.md (github: gh issue close --reason "not planned"; linear: the MCP tool that sets the issue state to Canceled; local: n/a). No KB entry (the KB is enhancements only).docs/out-of-scope/ following references/out-of-scope-kb.md: one file per concept (kebab-case), deduped by concept not keyword — append to an existing concept file's "Prior requests" rather than creating a near-duplicate. Then post a comment linking the record (AI disclaimer first) and close it as rejected via the close-as-rejected recipe in ../backlog/references/trackers.md (same recipe as the rejected-bug outcome — github not-planned / linear Canceled / local n/a).Present an AskUserQuestion restating that triage is done, with the applicable next-step routes as options (recommended first, plus Stop here). On selection, invoke the chosen /dobby:<skill> via the Skill tool; Stop here ends the turn.
/dobby:scope (Recommended) with the brief as the goal, to open a work session.docs/out-of-scope/; future triage will surface it. Stop here.insufficient → the maintainer goes back to the reporter for specifics; re-triage when they reply. Stop here.Interact with the user in their language. The brief, out-of-scope records, and any posted comments are in English; keep domain terms in their real-world form.
dobby:researcher → verdict is confirmed / failed / insufficient, reported to the maintainerreferences/agent-brief.md (interfaces & contracts, NEVER paths/line numbers)docs/out-of-scope/ per references/out-of-scope-kb.md, deduped by concept; already-implemented and rejected-bug outcomes write NO KB entry../backlog/references/trackers.md (github not-planned / linear Canceled / local n/a)../address-review/references/github-api.md; architect delegated verification and did no inline code edits/dobby:scope, or Stop here)Adapted from mattpocock/skills engineering/triage (portable half — verify-first, behavioral brief, out-of-scope KB; the tracker/state-machine is intentionally not ported).