rune-completion-gate

Validates agent completion claims against tool output evidence before commit.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dangvu008/VietTruyen --skill rune-completion-gate-dangvu008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rune-completion-gate
Source: https://github.com/dangvu008/VietTruyen/tree/main/.agents/skills/rune-completion-gate
Command: npx skills add https://github.com/dangvu008/VietTruyen --skill rune-completion-gate-dangvu008

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents frequently claim work is done — "tests pass", "bug fixed", "build succeeds" — without actual proof. This Skill acts as a lie detector that blocks unverified claims from reaching commit, catching the most common failure mode in AI-assisted development. ## Core Features & Use Cases - Claim-to-Evidence Matching: Extracts completion claims from agent output and matches each against real tool output (test stdout, build logs, git diffs), issuing CONFIRMED, UNCONFIRMED, or CONTRADICTED verdicts. - Stub & Loop Detection: Scans newly created files for placeholder code (TODO, NotImplementedError, empty returns) and audits tool-call patterns for observation loops that signal a stuck agent. - Plan Diff & Cross-Phase Checks: Diffs actual changes against phase plan files and verifies exports, routes, and end-to-end flows in multi-phase projects. - Use Case: After an agent reports "all 42 tests pass and the feature is implemented", run this gate to confirm the test output exists, the files are not stubs, and every planned task is checked off before allowing a commit. ## Quick Start Ask the agent to validate its completion claims with the completion gate before committing, requiring quoted command output as evidence for every claim.

Frequently Asked Questions about rune-completion-gate

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

FAQPage Schema
How do I verify an AI agent actually ran the tests it claims passed?

Require the agent to quote the test runner stdout showing pass counts, not just its narrative summary. The completion gate matches each claim like "tests pass" against actual Bash output and marks claims without evidence as UNCONFIRMED.

What is a completion gate in AI coding workflows?

A completion gate is a validation step that checks an agent's done claims against real evidence before commit. It classifies each claim as CONFIRMED, UNCONFIRMED, or CONTRADICTED and blocks progress unless every claim is confirmed.

How to detect when an AI agent creates stub or placeholder files?

Grep newly created or modified files for patterns like TODO, Placeholder, NotImplementedError, or functions that only return null or pass. Any detected stub converts the corresponding implemented claim into a CONTRADICTED verdict.

When should the completion gate be skipped?

The execution loop audit is skipped for nano or fast-rigor tasks with too few tool calls to analyze, and the plan diff check is skipped when no multi-phase plan file exists. Core claim validation always runs.

Why does the gate block when all claims seem confirmed?

A default-FAIL posture treats zero issues found as a red flag, triggering a skeptic sweep of the weakest claims. It also checks three axes — completeness, correctness, coherence — and flags any axis with no evidence as a gap.