Verification Before Completion
SkillDev toolsUse before claiming work is done, fixed, passing, complete, or ready to merge.
Then ask your AI: use the Verification Before Completion skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Add it as a step in a pipeline you build on Ahel, or connect Ahel to Claude, ChatGPT, Cursor, Claude Code or Codex and ask your AI to use it.
What this skill tells your AI
The instructions your AI receives, as published by rakuensoftware/aimee in skills/verification-before-completion/SKILL.md and read by Ahel’s review.
Completion claims require fresh evidence from this work session.
Before saying a task is done:
- Identify the command or inspection that proves the claim.
- Run it after the final code or document change.
- Read the exit code and relevant output.
- Report what passed and what could not be verified.
Avoid "should work", "looks good", or "probably fixed" when no verification ran. If verification is too expensive or blocked, say that directly and explain the residual risk.
Signals
- GitHub stars
- 187
- Forks
- 69
- Last commit
- Oct 2026
Advanced
- Item type
- skill
- Key
verification-before-completion-rakuensoftware- Source
- github.com/rakuensoftware/aimee
github.com/rakuensoftware/aimee