verify-skill
Use before claiming work is complete - runs tests, checks git status, verifies changelog
When & Why to Use This Skill
The verify-skill is an essential quality assurance tool designed to automate the 'Definition of Done' for software developers. It streamlines the final workflow by executing test suites, auditing git commit statuses, and validating changelog updates, ensuring that every task meets project standards before being marked as complete.
Use Cases
- Pre-Submission Validation: Run a comprehensive check of backend tests and git status before submitting code to ensure no regressions or uncommitted files are left behind.
- Automated Documentation Compliance: Verify that the CHANGELOG.md is properly updated with recent changes to maintain accurate project history and transparency.
- Multi-Language Environment Testing: Quickly execute tests across different environments, such as Node.js (npm) and Rust (cargo), within a single verification workflow.
- Workflow Standardization: Use as a mandatory checklist for AI agents or human developers to maintain high code quality and consistent repository state.
| name | verify-skill |
|---|---|
| description | Use before claiming work is complete - runs tests, checks git status, verifies changelog |
Verification Before Completion
Run this before saying "task complete" or "done".
Checklist
1. Tests Pass
npm run test:backend
Do NOT proceed if tests fail.
2. Code Committed
git status
All work-related files should be committed.
3. Changelog Updated
Check CHANGELOG.md [Unreleased] section has entry for this work. If not, run /changelog.
Quick Verification
# Run tests
cd src-tauri && cargo test
# Check status
git status
# Check changelog
head -20 CHANGELOG.md
See CLAUDE.md for project constraints.