compound-eng-verification-before-completionEnforces fresh verification evidence before any completion claim. Use when about to claim "tests pass", "bug fixed", "done", "ready to merge", or handing off...
Install via ClawdBot CLI:
clawdbot install iliaal/compound-eng-verification-before-completionGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated May 19, 2026
A developer is about to claim a feature is complete or a bug is fixed. This skill ensures they run the relevant test suite, check for lint errors, and verify the build before stating completion. It applies in daily stand-ups or when pushing code to a shared repository.
An automated CI system enforces this skill as a gate before merging pull requests. It runs tests, static analysis, and security scans, only allowing merges if all verification steps pass. This prevents faulty code from entering the main branch.
A freelance developer must demonstrate fresh verification evidence before claiming a task is done. For example, after fixing a client's website bug, they run the specific test case and show the output before invoicing. This reduces disputes over completion.
Students submitting code assignments are required to run and attach test output showing all tests pass. This instills discipline and ensures that claimed work is actually verified. Instructors can check the verification evidence before grading.
In industries like automotive or medical devices, developers must provide fresh verification evidence before marking any system function as complete. For instance, after updating firmware, they run a full battery of automated tests and document the exit code. This reduces risk of failure in production.
Offer a tool that plugs into development workflows to enforce verification-before-completion. It monitors commit messages and PR descriptions, flagging claims without fresh test output. Revenue comes from monthly or annual subscriptions per team.
Develop training courses and certification exams on verification-before-completion practices. Target individual developers and teams wanting to adopt this standard. Revenue from course fees and certification renewals.
Provide a free tier that enforces verification for up to 3 repositories, with premium features like detailed audit trails, historical trend analysis, and policy customization. Sell compliance reports to enterprise clients who need evidence for quality standards (e.g., ISO 26262).
💬 Integration Tip
Integrate with your existing CI/CD tool (e.g., GitHub Actions, Jenkins) to automatically check that pull request descriptions reference fresh test output or exit codes before merging.
Scored May 19, 2026
Multi-source deep research agent. Searches the web, synthesizes findings, and delivers cited reports. No API keys required.
Deep research on Xiaohongshu (小红书) topics. Use when user wants to research a topic, analyze trends, gather insights from top posts, or produce a summary repo...
Transparent, rigorous research with full methodology — not a black-box API wrapper. Conducts exhaustive investigation through mandated 2-cycle research per theme, APA 7th citations, evidence hierarchy, and 3 user checkpoints. Self-contained using native OpenClaw tools (web_search, web_fetch, sessions_spawn). Use for literature reviews, competitive intelligence, or any research requiring academic rigor and reproducibility.
Conduct open-ended research on a topic, building a living markdown document. Supports interactive and deep research modes.
Conduct comprehensive research independently. Find information, analyze sources, synthesize findings, and create detailed reports without human guidance.
Monitor Google Trends - get trending searches, compare keywords, and track interest over time. Use for market research, content planning, and trend analysis.