Enforce verification gate decisions by comparing planned and executed test commands.
npx skills add https://github.com/ldmrepo/agent-harness --skill test-gate
Please help me install this Agent Skill. Skill: test-gate Source: https://github.com/ldmrepo/agent-harness/tree/main/template/.claude/skills/test-gate Command: npx skills add https://github.com/ldmrepo/agent-harness --skill test-gate
This skill standardizes and enforces repository verification gates to prevent tasks and sessions from being marked as verified or approved without appropriate executed test evidence, ensuring consistent, auditable gate decisions across sessions.
Use the test-gate skill to evaluate executed verification commands, classify the gate outcome, and update the session summary and current task record accordingly.
High-intent search queries and answers about installing and using this skill.
To enforce a verification gate, you compare planned versus executed test commands, validate execution evidence quality, and write explicit gate outcomes into session summaries to drive approval decisions.
A quality gate check for session close evaluates whether required tests ran and whether evidence supports approval, classifying outcomes as passed, failed, pending, or not_evaluable for reviewers.
You validate test execution evidence by comparing planned versus executed test commands, assessing execution results and report quality, and detecting missing or contradictory evidence before approval.
Yes, you can determine gate depth by deciding whether smoke, task-level, integration, full-verify, or extended checks are required based on task type and repository policy for core code changes.
Session approvals fail because the verification gate detects missing or contradictory evidence, classifying the gate outcome as failed or not_evaluable and preventing unverified tasks from being approved.
Yes, test-gate operates with no external dependencies, applying its internal logic to repository verification, approval, and session-close scenarios across various task types.
MichielDeanIdentifies repository stack, conventions, and quality gates for future sessions.
Alex1980AlexReview OpenSpec change designs and update approval status in .openspec.yaml.
JaiminVadadoriyaDesign CI/CD pipelines for test execution with GitHub Actions and GitLab CI.
LeKayVerify story completion against design documents and update status.
