verification-before-completion
Verification Before Completion
Never declare work complete without running verification commands and confirming their output. Evidence before assertions, always.
Core Rule
Before claiming ANY of the following, you MUST run the relevant verification commands and confirm their output:
- "Tests pass"
- "The fix works"
- "Build succeeds"
- "Everything is green"
- "Ready to commit/push/merge"
- "Done" / "Complete" / "Finished"
What Counts as Verification
Acceptable evidence:
- Running the test suite and seeing the output (pass count, zero failures)
More from futuregerald/futuregerald-claude-plugin
adonisjs-best-practices
Use when building AdonisJS v6 applications, implementing features in AdonisJS, or reviewing AdonisJS code. Covers routing, controllers, validation, authentication, database patterns, testing, and error handling.
161baoyu-article-illustrator
Smart article illustration skill. Analyzes article content and generates illustrations at positions requiring visual aids with multiple style options. Use when user asks to "add illustrations to article", "generate images for article", or "illustrate article".
16turso-best-practices
Turso and libSQL best practices for SQLite-compatible cloud database development with edge distribution, embedded replicas, and vector search.
15better-auth-best-practices
Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.
12javascript-testing-patterns
Comprehensive JavaScript/TypeScript testing patterns for Jest, Vitest, and AdonisJS/Japa. Use when writing tests, reviewing test code, or debugging test failures.
12code-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
12