Verify fresh test, build, lint, or smoke results before reporting task completion.
npx skills add https://github.com/kanade0404/dotfiles --skill verify-done-kanade0404
Please help me install this Agent Skill. Skill: verify-done Source: https://github.com/kanade0404/dotfiles/tree/main/.opencode/skills/verify-done Command: npx skills add https://github.com/kanade0404/dotfiles --skill verify-done-kanade0404
This Skill stops premature completion claims by forcing a fresh verification check before you tell anyone a task is done.
Use the verify-done skill to check whether your latest verification evidence is fresh enough to safely report completion.
High-intent search queries and answers about installing and using this skill.
To prevent stale build or test results, enforce fresh verification evidence by running validation commands in the current session. The mechanism checks exit status, output details, and git status to reject completion claims when proof is missing or outdated.
Fresh verification evidence is proof that tests, lint, or smoke checks were successfully run in the current session before reporting a task as done. It requires checking exit status, reviewing output, and validating git state to ensure no uncommitted changes remain.
Verify git state before marking a task complete by running validation commands in the same session and checking the repository status. This ensures unfinished work or uncommitted changes are detected and completion language is rejected when evidence is stale or missing.
Yes, this verification approach works for pull requests and merges by enforcing current test, build, lint, or smoke results before replying with fixed or ready to merge. It requires running validation commands in the same session and reviewing git state.
Completion claims are rejected when evidence is stale to stop premature completion. The mechanism requires fresh verification evidence from the current session, checking exit status, output details, and git status so unfinished work or uncommitted changes are not missed.
The best way to enforce current validation checks is to require running test, build, lint, or smoke commands in the same session before a status update. This reviews exit status, output, and git state to reject completion language when evidence is stale.
MichielDeanIdentifies repository stack, conventions, and quality gates for future sessions.
Ab0umarVerify completion claims across commits, PRs, builds, and deployments with fresh evidence.
yocxy2Merge pull requests and verify production deployment health with canary checks.
alex-tgkExecute verification commands to validate tests, lint, and builds before commits.
