Use Cases
Before a developer commits code or creates a PR, this skill acts as a mandatory gate. The AI must execute full test commands, build commands, and lint checks sequentially, reading actual output and exit codes. Only after confirming all checks pass can it claim done or ready to commit. For example, when the AI says all tests pass, the skill requires showing actual npm test output evidence, not relying on previous runs or should pass guesses.
After fixing a bug, this skill mandates Red-Green regression verification: first confirm the new test indeed fails without the fix (proving the test catches the bug), then confirm the test passes after applying the fix (proving the fix works). This avoids the trap of tests pass but test the wrong thing. The skill requires showing complete regression verification evidence, not just stating I have written a regression test.
Skill File
Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
Follows the Gate Function four-step process:
Skip any step equals lying, not verifying.
Includes detailed red flag list (should, probably, seems to, etc.) and common rationalization excuse table.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
