qa-audit

Verify claims in sessions and transcripts against on-disk files and commits.

Updated May 16, 2026
One-click install
npx skills add https://github.com/organvm-i-theoria/_agent-ontology --skill qa-audit-organvm-i-theoria
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-audit
Source: https://github.com/organvm-i-theoria/_agent-ontology/tree/main/.agents/skills/qa-audit
Command: npx skills add https://github.com/organvm-i-theoria/_agent-ontology --skill qa-audit-organvm-i-theoria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agent sessions, PRs, and transcripts often contain claims about work done—files created, commits landed, content written—that may not match reality. This Skill audits those claims against the actual filesystem and repository state, producing a verification report instead of blindly trusting the record. ## Core Features & Use Cases - Claim Verification: Reads referenced session transcripts and artifacts fresh from disk, then checks each claim (file exists, content matches, commit landed) against on-disk reality. - Structured Verdicts: Classifies every claim as verified, false-positive, false-negative, or partial, so discrepancies are explicit rather than implied. - Owned Remediation List: Produces a remediation list with explicit owners, while stopping at verification—no remediation is executed without explicit approval. - Use Case: After an agent claims it refactored three modules and committed the changes, run this audit to confirm each file change and commit actually exists before merging or reporting the work as done. ## Quick Start Audit the claims in this session transcript against the current repository state and produce a verification report with owners for any remediation items.

Frequently Asked Questions about qa-audit

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

FAQPage Schema
When should I not rely on a transcript-based verification audit?▼

Avoid relying on it when artifacts cannot be re-read fresh from disk, since stale or cached copies undermine verification. It also does not replace code review of logic quality—it only checks whether claimed artifacts and commits actually exist.