inspector-qa

Validate code presence in src/ with grep checks before ticket approval.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/trevorc-ai/PPN-Antigravity-1.0 --skill inspector-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inspector-qa
Source: https://github.com/trevorc-ai/PPN-Antigravity-1.0/tree/main/.agent/skills/inspector-qa
Command: npx skills add https://github.com/trevorc-ai/PPN-Antigravity-1.0 --skill inspector-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-build QA gatekeeper that verifies code actually exists in the src/ directory before approving tickets.

Core Features & Use Cases

  • Final gatekeeper ensuring evidence exists in the codebase before a ticket is approved.
  • Enforces acceptance criteria, requires BUILDER IMPLEMENTATION COMPLETE, and performs grep-backed verification reporting.
  • Generates structured audit trails and clear failure reasons to speed up triage and rework.

Quick Start

Run the inspector on a new ticket to validate code presence and evidence before approval.

Frequently Asked Questions about inspector-qa

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

FAQPage Schema
How do I verify code existence in the src/ directory before approving tickets?

Post-build QA verification checks the src/ directory for actual code presence before ticket approval. It enforces acceptance criteria, requires BUILDER IMPLEMENTATION COMPLETE, and runs grep-backed checks to generate structured audit trails.

What is a post-build gatekeeper for code review?

A post-build gatekeeper validates that code actually exists in the src/ directory before a ticket is approved. It enforces workflow policies and reports structured evidence including acceptance criteria, builder sections, and audit results.

How do I automate grep-backed verification for acceptance criteria?

Automated grep-backed verification scans the src/ directory to confirm code existence and satisfaction of acceptance criteria. It enforces workflow policies, requires BUILDER IMPLEMENTATION COMPLETE, and reports structured evidence for triage.

Does this ticket approval gatekeeper require any dependencies?

No dependencies are required. The post-build QA gatekeeper operates independently to enforce code existence in the src/ directory, run grep-based checks, and report structured audit results before approving tickets.

Why does my post-build code review fail to catch missing implementations?

Post-build reviews fail when lacking automated grep-backed verification of the src/ directory. Enforcing acceptance criteria, requiring BUILDER IMPLEMENTATION COMPLETE, and generating structured audit trails speeds up triage and prevents approving incomplete code.

When do I need automated verification before approving a ticket?

Automated verification is needed during post-build review scenarios to ensure acceptance criteria are fully satisfied. It validates code existence in the src/ directory, requires BUILDER IMPLEMENTATION COMPLETE, and runs grep-backed checks before approval.