verify
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—ensuring changes are genuinely complete before you move on.
Verify provides evidence that code changes work by running tests and validation commands before completion.
AI-generated summary based on this skill's SKILL.md
Install
zereight/gitlab-mcp/verify · repository language: TypeScript
git clone https://github.com/zereight/gitlab-mcp
cp -r gitlab-mcp/.github/skills/verify ~/.claude/skills/verifyFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I verify my code changes work?
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—so you know your changes are genuinely complete before moving on.
What does verify this works actually mean?
Verify this works means running automated checks—tests, linters, type checkers, and custom validators—to 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.
Can verify check for test coverage gaps?
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.
How does verify validate behavior with concrete evidence?
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—or reveals exactly where it doesn't—before deployment.
What happens when verify finds failures?
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.
Does verify run before task completion?
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—and a record of what was checked—before you move forward.
SKILL.md
rendered from the published skill — quoted content, verbatim
Verify
Turn vague "it should work" claims into concrete evidence.
Workflow
- Identify the exact behavior that must be proven
- Prefer existing tests first
- If coverage is missing, run narrowest direct verification commands
- If direct automation not enough, describe manual validation steps
- Report only what was actually verified
Verification Order
- Existing tests
- Typecheck / build
- Narrow direct command checks
- Manual or interactive validation
Rules
- Do not say a change is complete without evidence
- If a check fails, include the failure clearly
- If no realistic verification path exists, say so explicitly
- Prefer concise evidence summaries over noisy logs
Output
- What was verified
- Which commands/tests were run
- What passed
- What failed or remains unverified
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.github/skills/verify/SKILL.md