agent-code-quality-gate

Verify coding agent completion claims through diff inspection and test verification.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/MinhDuyDEV/mdpi --skill agent-code-quality-gate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-code-quality-gate
Source: https://github.com/MinhDuyDEV/mdpi/tree/main/.pi/skills/agent-code-quality-gate
Command: npx skills add https://github.com/MinhDuyDEV/mdpi --skill agent-code-quality-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents coding agents from claiming incomplete or unreliable work by enforcing a structured quality gate before completion reports.

Core Features & Use Cases

  • Completion Verification: Checks scope, design fit, simplicity, duplication, tests, verification evidence, and regression risks before declaring work complete.
  • Agent Reliability Review: Detects common failure modes such as hallucinated APIs, fake confidence, unverified subagent output, and speculative abstractions.
  • Use Case: Use this Skill after a feature implementation or bugfix to ensure the diff is focused, behavior is tested, and completion evidence is clearly documented.

Quick Start

Use the agent-code-quality-gate skill to review my completed code changes and identify any missing verification or quality issues.

Frequently Asked Questions about agent-code-quality-gate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code changes before an agent reports task completion?▼

To verify code changes before completion, enforce a quality gate that requires systematic diff inspection, behavioral validation, and test verification to assess scope and regression risks.

What is an agent workflow quality gate for code review?▼

An agent workflow quality gate is a verification process that prevents coding agents from claiming completion without checking implementation scope, design fit, evidence, and regression risks.

How do I prevent coding agents from reporting incomplete or hallucinated work?▼

Prevent incomplete work by applying a quality gate that detects agent failure modes like hallucinated APIs, fake confidence, and speculative abstractions through systematic diff inspection and test verification.

Can I use this verification gate for refactoring and migration code changes?▼

Yes, you can use this verification gate for feature work, bugfixes, refactors, migrations, and subagent-generated changes to ensure the diff is focused and behavior is tested.

What's the best way to review subagent-generated code changes?▼

The best way to review subagent changes is enforcing a structured quality gate that checks for unverified output, duplication, and missing verification evidence before declaring the work complete.

Why does my coding agent claim tasks are done without running tests?▼

Coding agents claim completion without tests due to unverified subagent output and fake confidence; enforcing a completion verification gate prevents this by requiring test verification evidence.