菜单
Confirm a function, argument, option, type, callback, or CLI flag actually exists with the signature you think — before you call it. Use whenever you're about to use an API you're not certain of, or any time you'd otherwise be guessing. Stops hallucinated calls before they're written.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Drain this repo's .agent/tasks/ queue autonomously and run-to-completion, taking EACH task to a ship-ready bar — claim a 00_todo/ task (`coop tasks claim`), build it, gate it green, self-review it against the .agent/rules KB and every hat, ITERATE until clean, COMMIT it on its own, then `coop tasks done` — without quitting early. Use to "work all the tasks" / drain a backlog / run an unattended sweep.
Cut a versioned release of coop — derive the semver bump from the `## Unreleased` changelog, finalize + annotated-tag it, then (only on explicit confirmation) push the `v*` tag that triggers the public GoReleaser build. Refuses a docs-only no-op release. Use when asked to "cut / ship / tag a release", "publish a release", or "bump the version".
The heavyweight pre-merge review — convene a board of expert hats (correctness, this repo's own rules, security, plus PM/UX/maintainer and any hat the change earns) as parallel reviewers, then synthesize ONE ranked verdict and an ordered plan to fix everything. Reads the project's OWN `.agent/rules/` and runs its OWN gate — no hardcoded laws. Read-only. Works on local changes, a commit, a range, a branch/ref, or a PR. Use before landing anything substantial, or when you want a thorough multi-perspective review.
Execute an approved plan step-by-step, with the repo's gate between steps and no scope creep. Use when implementing a planned change, working a checklist, or the user says "go" / "implement it" / "do the plan". Stops and reports on the first red gate.
Design an opinionated, boring-by-default implementation plan before writing code. Use when a change spans more than one file or context, when the approach isn't obvious, or when asked to plan/design/think through a feature. Produces a small-step, verifiable plan to approve before /work.
Root-cause a crash, panic, failing test, or wrong behavior — reproduce, read the real error, trace to the actual cause, then propose the minimal fix. Use when something fails or misbehaves and you need the cause, not a guess. Never edit a test to make a real failure pass.
| name | verify-api |
| description | Confirm a function, argument, option, type, callback, or CLI flag actually exists with the signature you think — before you call it. Use whenever you're about to use an API you're not certain of, or any time you'd otherwise be guessing. Stops hallucinated calls before they're written. |
| argument-hint | <the function/option/flag you're unsure about> |
| allowed-tools | Read, Grep, Glob, Bash, WebFetch |
A hallucinated function/arg/flag costs far more than the lookup. When in doubt, check before you write. Stop at the first rung that gives a definitive answer; local sources beat the web — they're exact for the versions this repo uses.
rg -n 'def my_function|fn myFunction|function myFunction' <dir>
node_modules/, deps/, vendor/, the site-packages path — not a guess
or a newer doc. Confirm the version from the lockfile first if it matters.<tool> --help # real flags for this installed version
<tool> help <cmd>
Report what you confirmed (the signature) and where you found it. If you can't confirm it, say so — and pick a different API you can verify.