verification-before-completion

Files (1)

• SKILL.md

SKILL.md (first lines)

# Verification Before Completion

## Rule

You MUST run verification commands and read their output before telling the user a task is done.

## Never say these without verification

- "This should work now"
- "The fix is in place"
- "I've completed the changes"
- "Everything should be good"

## Verification steps (in order)

1. **If tests exist**: Run `npm test` and read output
2. **If build exists**: Run `npm run build` and read output
3. **If lint exists**: Run `npm run lint` and read output
4. **Read the actual output** — don't assume success from exit code alone

## If verification fails

- Fix the issue
- Re-run verification
- Only report completion after ALL checks pass

## If no verification commands exist

- State explicitly: "No automated verification available. Please review manually."
- Do NOT claim the task is complete without saying this

From nic611/claude-engineering-kit, MIT.

More from nic611/claude-engineering-kit