메뉴
Use automatically during development workflows when making claims about tests, builds, verification, or code quality requiring concrete evidence to ensure trust through transparency.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/TheBushidoCollective/han --skill proof-of-work명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
Review current branch changes against REVIEW.md guidelines
Use when kotlin coroutines for structured concurrency including suspend functions, coroutine builders, Flow, channels, and patterns for building efficient asynchronous code with cancellation and exception handling.
Use when building modular Angular applications requiring dependency injection with providers, injectors, and services.
SOC 직업 분류 기준
| name | proof-of-work |
| user-invocable | false |
| description | Use automatically during development workflows when making claims about tests, builds, verification, or code quality requiring concrete evidence to ensure trust through transparency. |
| allowed-tools | ["Write","Edit","Read","Bash","Grep"] |
Show, don't tell. Never make claims about code verification without providing concrete evidence.
Trust through transparency. Every assertion about code quality, test results, builds, or verification must be backed by actual command output, not summaries or assumptions.
When implementing features:
USE Write/Edit tools to make changes
Show tool results
Verify changes exist
ls -la /path/to/file.exRemember: If you didn't use Write/Edit tools, it didn't happen.
NEVER EVER trust agent completion reports without verification.
This is a zero-tolerance rule. Agent reports are NOT proof - they are claims requiring verification.
When you delegate work to a subagent:
After ANY agent completes, you MUST verify work was actually done:
# 1. Verify files were actually modified
git status --short
# 2. Verify actual changes exist
git diff --name-only
# 3. Verify specific file exists (if agent claimed to create it)
ls -la /path/to/file
# 4. Verify file content (spot check)
cat /path/to/file | head -20
If git status shows clean working tree → NOTHING was done, regardless of agent report.
| Agent Claim | Required Verification |
|---|---|
| "Successfully created X" | ls -la /path/to/X - prove file exists |
| "Modified files A, B, C" | git status - prove files show as modified |
| "Changes made to Y" | git diff Y - prove actual changes exist |
| "Implementation complete" | git diff --stat - prove work was done |
| "Added tests to Z" | cat Z - prove tests actually exist |
| "Updated configuration" | git diff config/ - prove config changed |
1. Delegate to agent
2. Agent reports completion
3. ⚠️ STOP - DO NOT TRUST REPORT ⚠️
4. Run verification commands (git status, ls, cat, etc.)
5. If verification fails → Agent did NOT complete work
6. If verification passes → THEN report to user WITH PROOF
❌ NEVER report to user:
✅ ALWAYS report with proof:
# After agent completes, verify:
$ git status --short
M apps/api/lib/users/worker.ex
A apps/api/test/users/worker_test.exs
# Prove files exist:
$ ls -la apps/api/test/users/worker_test.exs
-rw-r--r-- 1 user staff 2847 Nov 7 14:32 apps/api/test/users/worker_test.exs
# Spot check content:
$ head -10 apps/api/test/users/worker_test.exs
defmodule YourApp.Users.UserTest do
use YourApp.DataCase
...
Then report: "Agent completed. Verification proves 2 files modified (evidence above)."
The user must be able to trust your reports. Agent reports without verification are worthless.
This is non-negotiable. Failure to verify agent work is unacceptable.
Apply this skill whenever claiming:
❌ Never say without proof:
✅ Always provide actual output:
# Tests
$ mix test
Finished in 42.3 seconds
1,247 tests, 0 failures
# Linting
$ MIX_ENV=test mix lint
Running Credo... ✓ No issues found.
# Types
$ yarn ts:check
✓ 456 files checked, 0 errors
# CI Pipeline
$ glab ci status
Pipeline #12345: passed ✓
URL: https://gitlab.com/.../pipelines/12345
❌ WRONG:
✅ RIGHT:
mix test to verify..."❌ NEVER claim success from partial runs:
# Only ran 50 tests of 1,247
Running ExUnit tests...
50 tests, 0 failures
# STOPPED HERE - did not complete
"Tests pass" ❌ FALSE - only partial run
✅ ALWAYS run to completion:
# Full suite completed
Finished in 42.3 seconds
1,247 tests, 0 failures # ALL tests ran
"Full test suite passes: 1,247 tests, 0 failures" ✅ TRUE
$ MIX_ENV=test mix lint
✓ No issues found.
$ mix test
1,247 tests, 0 failures
$ yarn graphql:compat
✓ No breaking changes
$ glab ci status
Pipeline #12345: passed ✓
Then claim: "All verification passed (evidence above)."
Stop and provide proof if you catch yourself saying:
Implementation: Run verification → Show complete output → Report with evidence → Wait for approval
Code review: Reference line numbers (file.ts:123), quote issues,
show analyzer output
Debugging: Show full errors, stack traces, reproduction steps with output