メニュー
Ground progress and completion claims in fresh tool evidence. Use before reporting work complete, fixed, passing, ready to commit, or ready to publish, especially after agent delegation.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/nwiizo/dotfiles --skill home-verification-before-completionコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Add config to this macOS dotfiles repo. Use for env vars, fish abbreviations/functions/plugins, direct symlinked config files, tool integrations, shared agent config, and app config such as Neovim, Ghostty, Warp, Git, Bat, Atuin, tealdeer, and gh.
Add a package to this macOS dotfiles repo. Use when the user asks to install, add, or migrate a CLI package or GUI app, for example "add jq", "ripgrep を入れて", "lazygit 入れたい", "brew install foo を repo 管理に", "kubectl 追加して". Homebrew owns binaries here; update Brewfile, validate with brew bundle, apply with brew bundle, and verify the executable.
実装前の計画・設計・意思決定を、1問ずつの徹底インタビューで叩いて固める。共有理解に達するまで実装しない。Invoke manually before non-trivial implementation when a plan or design already exists and needs stress-testing.
| name | home-verification-before-completion |
| description | Ground progress and completion claims in fresh tool evidence. Use before reporting work complete, fixed, passing, ready to commit, or ready to publish, especially after agent delegation. |
Report the observed state, not the expected state. Verification strength should match the claim and the risk of the change.
Before a progress or completion report:
| Claim | Evidence |
|---|---|
| Tests pass | Relevant test command completed with zero failures |
| Linter is clean | Relevant lint command completed with zero errors |
| Build succeeds | Build command exited successfully |
| Bug is fixed | Original symptom or regression test now passes |
| Requirements are met | Acceptance checklist checked against artifacts and results |
| Agent work is complete | Inspect the diff or artifact, then run independent verification |
A formatter does not prove a build. Unit tests do not prove an unrun integration suite. An agent's status message does not prove its artifact.
Use a red-green check when it is practical and materially increases confidence: show that the regression test fails without the fix and passes with it. Do not force destructive or high-cost reversions merely to satisfy the pattern; explain the safer evidence used instead.
Lead with the outcome. Include the verification command and observed result in plain language, then list any remaining unverified area. Never describe a skipped or failed check as passing.