메뉴
Verify system claims and test results through independent validation rather than trusting assumptions
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/wojons/skills --skill trust-but-verify명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | trust-but-verify |
| description | Verify system claims and test results through independent validation rather than trusting assumptions |
| license | MIT |
| compatibility | opencode |
| metadata | {"audience":"developers","category":"testing"} |
Apply skeptical verification to all system claims, test results, and assumptions through independent validation rather than blind trust, preventing false confidence and accelerating issue detection.
Use this skill when:
Extract claims from:
Categorize claims by:
Select appropriate verification methods:
Coordinate with other test types:
Challenge assumptions deliberately:
Execute verification with different contexts:
Compare claims vs verification results:
Generate actionable insights:
# Verify test results claims
npm run verify:test-results -- --test-suite "user-authentication"
npm run verify:test-coverage -- --module "payment-processing"
# Verify feature claims
npm run verify:feature -- --feature "checkout-flow" --claim "handles 1000 concurrent users"
npm run verify:feature -- --feature "report-generation" --claim "exports to PDF format"
# Verify system operational claims
npm run verify:system-health -- --component "database" --claim "redundant and fault-tolerant"
npm run verify:system-performance -- --endpoint "/api/orders" --claim "response < 200ms"
# Verify progress/memory claims
npm run verify:progress -- --task "implement-payment-webhook" --claim "completed and tested"
npm run verify:documentation -- --section "api-reference" --claim "accurately describes endpoints"
# Comprehensive verification
npm run verify:all-claims # Verify all identified claims
npm run verify:critical-claims # Verify only critical claims
npm run verify:stale-claims # Verify claims not recently checked
# Integration with other testing
npm run verify:with -- --test-type chaos --claim "system-resilient"
npm run verify:with -- --test-type security --claim "no-vulnerabilities"
npm run verify:with -- --test-type usability --claim "user-friendly"
Trust But Verify Report
──────────────────────────────
Verification Context: Pre-production release validation
Total Claims Identified: 47
Claims Verified: 23 (priority order)
Verification Duration: 2 hours 15 minutes
Critical Claim Verification Results:
1. Claim: "Payment processing tests pass with 100% coverage"
Source: CI/CD pipeline report
Verification Strategy: Independent test execution + coverage analysis
Result: ❌ DISCREPANCY FOUND
- Tests pass but don't validate currency conversion rates
- Coverage shows 100% but misses error handling paths
- Test data uses only USD, missing other currencies
Recommendation: Add currency conversion tests, expand test data
2. Claim: "System handles 5000 concurrent users"
Source: Performance test report from 2 weeks ago
Verification Strategy: Fresh load test with different patterns
Result: ⚠️ PARTIALLY VERIFIED
- System handles 5000 users but response time degrades by 300%
- Database connection pool exhausted at 4500 users
- CPU usage reaches 95% at target load
Recommendation: Optimize database connections, add autoscaling
3. Claim: "User registration feature complete"
Source: Project management system
Verification Strategy: End-to-end testing + security review
Result: ✅ VERIFIED
- Registration flow works correctly
- Email verification functional
- Password security requirements enforced
- No security vulnerabilities found
4. Claim: "Monitoring alerts configured for all critical errors"
Source: DevOps runbook
Verification Strategy: Error injection + alert monitoring
Result: ❌ DISCREPANCY FOUND
- Database connection errors not alerting
- Payment gateway timeouts not monitored
- Alert thresholds too high for business impact
Recommendation: Review and update alert configuration
5. Claim: "Backup system tested and functional"
Source: System documentation
Verification Strategy: Actual backup restore test
Result: ⚠️ PARTIALLY VERIFIED
- Backup creation works
- Restore process documented but untested
- Restore time exceeds RTO (Recovery Time Objective)
Recommendation: Test full restore, optimize restore process
Verification Confidence Assessment:
- High Confidence: 8 claims (thoroughly verified)
- Medium Confidence: 10 claims (partially verified)
- Low Confidence: 5 claims (insufficient verification)
- Failed Verification: 5 claims (discrepancies found)
Critical Issues Requiring Attention:
1. Payment currency conversion untested (business risk: high)
2. Database connection pool limits scalability (performance risk: high)
3. Missing critical error alerts (operational risk: medium)
4. Backup restore untested (recovery risk: medium)
Verification Effectiveness:
- False positives prevented: 3 (would have caused production issues)
- Assumptions challenged: 12 (revealed hidden risks)
- Verification time vs value: High ROI (2 hours prevented days of issues)
- Recommendations generated: 7 actionable improvements
Next Steps:
1. Address critical discrepancies before release
2. Improve test coverage for payment processing
3. Optimize database connection management
4. Update monitoring and alert configuration
5. Schedule regular verification for high-risk claims