메뉴
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에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/nwiizo/dotfiles --skill home-verification-before-completion명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
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.
SOC 직업 분류 기준
SKILL.md 표시 중
| 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.
