qa-slice

Evaluate GitHub issue slice acceptance criteria against fetched evidence for deterministic verdicts.

Updated Mar 22, 2026

Search Tags:#evidence #deterministic #grading #github-api #slice #qa-gate

Ready to run

npx skills add https://github.com/pollockjj/grader-in-the-loop --skill qa-slice

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-slice
Source: https://github.com/pollockjj/grader-in-the-loop/tree/main/.claude/skills/qa-slice
Command: npx skills add https://github.com/pollockjj/grader-in-the-loop --skill qa-slice

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The QA gate provides a deterministic mechanism to evaluate GitHub issue slice submissions against their acceptance criteria by fetching and validating evidence from the issue body, commits, CI status, and test logs, then emitting a structured PASS or HOLD verdict.

Core Features & Use Cases

Extracts acceptance criteria from the issue body and compares them against fetched artifacts (diffs, CI checks, test logs).
Produces a per-criterion evidence table and a single, deterministic decision, enabling clear traceability and reproducibility.
Use when reviewing a slice submission, gating an implementation, or auditing slice completeness.

Quick Start

Run the QA gate on a Slice submission to obtain a deterministic PASS or HOLD verdict.

Frequently Asked Questions about qa-slice

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

FAQPage Schema

How do I automate QA gating for GitHub issue slice submissions?▼

Automate QA gating for GitHub issue slice submissions by evaluating acceptance criteria against fetched evidence from issue bodies, commit diffs, CI status, and test logs to produce deterministic per-criterion MET or NOT MET verdicts.

What is deterministic evidence-only decision making for code review?▼

Deterministic evidence-only decision making fetches artifacts like diffs, CI checks, and test logs to validate acceptance criteria, emitting a structured PASS or HOLD verdict with clear traceability and no ambiguity.

How do I verify acceptance criteria against commit diffs and CI status?▼

Verify acceptance criteria against commit diffs and CI status by extracting criteria from the issue body and comparing them against fetched artifacts to generate a per-criterion evidence table with a single deterministic decision.

Can I use GitHub API data to gate implementation reviews with test logs?▼

Use GitHub API data to gate implementation reviews by operating across issue bodies, commit diffs, CI status, and test logs to audit slice completeness and produce a reproducible PASS or HOLD verdict.

What's the best way to audit slice completeness without ambiguous outcomes?▼

Audit slice completeness without ambiguous outcomes by enforcing evidence-only decision making that fetches and validates artifacts, producing a deterministic per-criterion MET or NOT MET verdict table.

When do I need a deterministic QA gate for slice submissions?▼

Use a deterministic QA gate when reviewing a slice submission, gating an implementation, or auditing slice completeness to ensure acceptance criteria are evaluated against fetched evidence with reproducible outcomes.