verify
Verify Builds and Recover from Errors
Failed builds and broken tests waste development time. This skill verifies code builds, recovers from common errors, and applies approved review fixes while enforcing quality standards that prevent test tampering.
Download the skill ZIP
Upload in Claude
Go to Settings โ Capabilities โ Skills โ Upload skill
Toggle on and start using
Test it
Using "verify". Verify that my recent changes build successfully
Expected outcome:
- Build verification complete
- Build: Success
- Type check: Passed
- Tests: 15 passed, 0 failed
- Lint: No issues found
- Ready to proceed to next step
Using "verify". Help me recover from these build errors
Expected outcome:
- Analyzing error patterns
- Found: Cannot find module 'express'
- Attempting: npm install express
- Build: Success after recovery
- Note: 2 retry attempts remaining
Security Audit
SafeThis is a documentation-only skill containing no executable code. All 137 static findings are false positives. The skill provides guidelines for build verification, error recovery, and code review processes with strong quality guardrails that prevent test tampering and enforce proper development practices.
Risk Factors
โ๏ธ External commands (118)
๐ Network access (1)
๐ Filesystem access (2)
Quality Score
What You Can Build
Post-Implementation Verification
Automatically verify builds and tests pass after implementing new features or fixes
Apply Review Feedback
Quickly apply approved automated fixes from code reviews like formatting and unused code removal
CI Pipeline Recovery
Automatically recover from common CI failures without manual intervention
Try These Prompts
I just finished implementing the new feature. Can you verify that the build passes and all tests are working correctly?
The build is failing with TypeScript errors. Can you help fix these compilation issues?
The code review found several issues. Can you apply the automated fixes for unused imports and formatting?
The tests are failing with assertion errors. Try to automatically fix the issues or escalate if needed.
Best Practices
- Always verify builds after making changes before submitting pull requests
- Use the skill quality guardrails to prevent test tampering shortcuts
- Review the diff before approving automated fixes to understand changes
Avoid
- Skipping tests or removing assertions to make builds pass
- Disabling lint rules instead of fixing underlying code issues
- Using continue-on-error to bypass CI checks without resolving root causes
Frequently Asked Questions
Which programming languages are supported?
What happens if automatic fixes fail?
Can it fix all types of errors?
Is my code protected from harmful changes?
How does it integrate with existing CI?
Which AI platforms support this skill?
Developer Details
File structure
๐ error-recovery/
๐ doc.md
๐ review-aggregate/
๐ doc.md
๐ review-apply-fixes/
๐ doc.md
๐ verify-build/
๐ doc.md
๐ SKILL.md