{"enrichment":{"faq":[{"a":"Verify helps you turn uncertain claims into concrete proof by running existing tests, type checks, and targeted validation commands. Run your test suite, check types, and execute any domain-specific validators tied to your change. Verify reports exactly what passed, what failed, and what remains unverified\u2014so you know your changes are genuinely complete before moving on.","q":"How do I verify my code changes work?"},{"a":"Verify this works means running automated checks\u2014tests, linters, type checkers, and custom validators\u2014to prove your code behaves as intended. Verify collects the results and shows you the evidence: which checks passed, which failed, and which gaps remain. This transforms a vague claim into measurable, documented proof.","q":"What does verify this works actually mean?"},{"a":"Verify can identify test coverage gaps by running your existing test suite and reporting which parts of your code lack coverage. Once gaps are found, you can write targeted tests to fill them. This ensures your changes are backed by concrete test evidence before you mark the task complete.","q":"Can verify check for test coverage gaps?"},{"a":"Verify validates behavior by executing your tests, type checks, and validation commands, then documenting the results. It shows you what passed, what failed, and what wasn't tested. This concrete evidence proves your implementation works\u2014or reveals exactly where it doesn't\u2014before deployment.","q":"How does verify validate behavior with concrete evidence?"},{"a":"When Verify finds failures, it reports them clearly: which checks failed, why they failed, and what needs fixing. This documentation helps you understand what's broken and what to fix next. Verify ensures you see all failures before marking work complete, not after deployment.","q":"What happens when verify finds failures?"},{"a":"Yes, Verify is designed to run before you mark a task complete. It proves your code changes work by running tests, checks, and validators. This verification step ensures you have concrete evidence of functionality\u2014and a record of what was checked\u2014before you move forward.","q":"Does verify run before task completion?"}],"shadow_tags":["evidence-based-validation","change-confirmation","pre-completion-checks","test-first-verification","proof-of-correctness","behavior-validation","quality-gates","concrete-testing"],"summary_rewrite":"Verify turns uncertain claims into concrete proof by running existing tests, type checks, and targeted validation commands. It reports exactly what passed, what failed, and what remains unverified\u2014ensuring changes are genuinely complete before you move on."},"files":[{"bytes":1021,"path":".github/skills/verify/SKILL.md","sha256":"a20474e601babb74fede7b79539d341241efce26ddacf986f89c82e50df892c3","url":"https://skillfed.io/files/zereight/gitlab-mcp/verify/dc744e4d/SKILL.md"}],"id":"zereight/gitlab-mcp/verify","links":{"html":"https://skillfed.io/zereight/gitlab-mcp/verify","md":"https://skillfed.io/zereight/gitlab-mcp/verify.md","repo":"https://github.com/zereight/gitlab-mcp"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":330,"language":"TypeScript","last_updated":"2026-07-27","license":"MIT","name":"verify","publisher":"zereight","stars":1847},"relations":{"similar":[{"id":"zereight/gitlab-mcp/ultraqa"},{"id":"zereight/gitlab-mcp/review"},{"id":"zereight/gitlab-mcp/ralplan"},{"id":"zereight/gitlab-mcp/ultrawork"},{"id":"zereight/gitlab-mcp/trace"},{"id":"zereight/gitlab-mcp/ai-slop-cleaner"},{"id":"zereight/gitlab-mcp/status"},{"id":"zereight/gitlab-mcp/plan"},{"id":"zereight/gitlab-mcp/deep-dive"},{"id":"zereight/gitlab-mcp/ralph"}]},"slug":{"owner":"zereight","repo":"gitlab-mcp","skill":"verify"},"version":"dc744e4d"}