メニュー
Mandatory verification protocol after code changes for Go projects. Use after any code modification to ensure quality.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/robert-chiniquy/dotfiles --skill post-change-verificationコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Sweep open issue trackers, TODOs, active branches, and source evidence to find narrowly scoped, independent, verifiable tasks suitable for remote agents or parallel delegation. Use when asked to find pebbles, small delegatable work, fire-and-forget candidates, backlog slices, ready items, or pool/task combinations.
Write a scorecard — a dark, skimmable one-screen readout of the current situation in the user's work, rendered as a terminal (TUI) artifact by the `scorecard` binary from a structured markdown file. Use ONLY when the user explicitly asks for a scorecard (or a "readiness card" / "go/no-go card" / "coverage snapshot card"). A plain "status", "status?", or other status/situation question gets a prose answer, never this skill. NOT a web page — output is the dark TUI. Preserves older scorecards by datestamp. Triggers on: scorecard, readiness card, go/no-go card, coverage snapshot card.
Present comparisons as narrow ASCII bar charts in the terminal. Use when user asks to compare items, metrics, counts, or coverage between things.
| name | post-change-verification |
| description | Mandatory verification protocol after code changes for Go projects. Use after any code modification to ensure quality. |
After creating, modifying, generating, or refactoring Go code (not after read-only analysis, audits, or docs-only work), run IN ORDER — prefer make targets over direct commands:
make fmt (else go fmt ./...)make lint (else golangci-lint run)make build (else go build ./...)make test (else go test ./path/to/modified/..., or go test ./...)Target: ZERO errors and ZERO warnings across all steps.
Pre-existing issues never block task completion; issues caused by your changes always do.
Do not block on tooling gaps — mark the step and continue:
SKIPPED (command not found)SKIPPED (timeout)SKIPPED (execution error: [reason])Include this in task completion output:
=== POST-CHANGE VERIFICATION ===
Format: [PASSED | FAILED | SKIPPED (reason)]
Lint: [PASSED | FAILED] ([X] errors, [Y] warnings)
Build: [PASSED | FAILED] ([X] errors)
Tests: [PASSED | FAILED] ([X]/[Y] passed)
Pre-existing issues: [NONE | list with file:line]
=== [TASK COMPLETE | VERIFICATION FAILED] ===
Unfixed issues caused by the change end with === VERIFICATION FAILED - FIX ISSUES BEFORE COMPLETING ===.
Go projects MUST have Makefile targets fmt, lint, build, test (plus combined verify: fmt lint build test). If targets are missing, fall back to direct commands and note it in the report.