When is the best time to invoke this skill?

Use it before any significant delivery, after major implementation changes, or whenever you need an objective confidence check before handing work off to another person or system.

How are the quality scores calculated?

Scores are based on a 0-100 scale: 95-100 (Excellent/Deliver), 85-94 (Good/Deliver with notes), 75-84 (Acceptable/Minor issues), and below 75 (Needs Work/Return to development).

Can this skill identify security vulnerabilities?

Yes, as part of the Risk Evaluation step, the skill explicitly checks for security vulnerabilities and potential technical risks that could impact the production environment.

What is the 150% Check Rule?

It is a methodology that requires verifying 100% of the core requirements (goals, correctness, completeness) plus an additional 50% of enhancements, including edge cases, side effects, and future-proofing.

Integrity Check 150

Name: Integrity Check 150
Author: MykhailoDmytriakha

byMykhailoDmytriakha

보안 및 테스팅

Performs a rigorous final quality assurance check to verify goal alignment, technical correctness, and implementation completeness.

소개

Integrity Check 150 is a specialized Claude Code skill designed to provide a comprehensive final review of any significant work output before delivery. It employs a '150% Check Rule' that validates 100% of core requirements while evaluating an additional 50% of enhancements like edge cases, context fit, and future-proofing. By producing an objective 0-100 quality score and a detailed delivery status report, this skill helps developers identify residual risks, surface hidden technical debt, and ensure high-confidence handoffs for every task.

주요 기능

Multi-dimensional quality scoring (0-100) with honest self-critique logic
0 GitHub stars
Structured delivery status reports (Ready, Conditional, or Not Ready)
Contextual integration check to ensure compatibility with existing environments
Comprehensive risk assessment identifying edge cases and security gaps
Detailed goal alignment verification against original user objectives

사용 사례

Final validation of a feature implementation before submitting a pull request
Post-refactoring confidence check to ensure logic coherence and technical accuracy
Systematic audit of technical documentation or architecture plans before team handoff

소개

주요 기능

Multi-dimensional quality scoring (0-100) with honest self-critique logic
0 GitHub stars
Structured delivery status reports (Ready, Conditional, or Not Ready)
Contextual integration check to ensure compatibility with existing environments
Comprehensive risk assessment identifying edge cases and security gaps
Detailed goal alignment verification against original user objectives

사용 사례

Final validation of a feature implementation before submitting a pull request
Post-refactoring confidence check to ensure logic coherence and technical accuracy
Systematic audit of technical documentation or architecture plans before team handoff