verify-before-claiming
Use when about to claim work is complete, fixed, passing, installed, synced, or ready for review.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use when about to claim work is complete, fixed, passing, installed, synced, or ready for review.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when ingesting, refreshing, listing, searching, or deleting a local corpus with Blackbird code search and `gh blackbird search --fileset`.
Use when reaching for `gh blackbird` (Blackbird code search) for cross-repo lexical, symbol, or semantic search on GitHub — finding callers, ownership, or how systems work without cloning.
Use when creating a GitHub pull request, or when updating an existing PR's title or body so it matches what the code actually does.
Use when authoring or substantially editing a design doc, architecture doc, or subsystem explanation — the "here's what's there and why" companion to an ADR's terse decision record.
Use when creating a repo-tracked multi-agent planning PR for a large project, especially when phases, living docs, parallel agent prompts, and cross-PR coordination are needed.
Use when about to call a library, crate, or framework API you haven't verified, when a dependency's behavior is surprising, when training-data memory might be stale, or when investigating how a dependency actually behaves.
| name | verify-before-claiming |
| description | Use when about to claim work is complete, fixed, passing, installed, synced, or ready for review. |
Evidence before assertions.
Before saying work is complete, fixed, passing, installed, synced, or ready:
| Claim | Proof |
|---|---|
| Tests pass | Test command exits 0 with no failures |
| Lint passes | Lint command exits 0 |
| Build succeeds | Build command exits 0 |
| Bug fixed | Original reproduction no longer fails |
| Skill installed | Sync/install command succeeds and target link/file exists |
| Requirements met | Checklist maps each requirement to code/docs/verification |
Do not rely on "should", prior runs, or another agent's success report.