qa-report-triage

Triages accumulated QA job reports into a severity-sorted action pipeline and applies approved fixes.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/arayaroma/ether --skill qa-report-triage-arayaroma
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-report-triage
Source: https://github.com/arayaroma/ether/tree/main/skills/qa-report-triage
Command: npx skills add https://github.com/arayaroma/ether --skill qa-report-triage-arayaroma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Findings from local QA jobs pile up in .ether/qa/jobs/*/report.md files with no structured way to review, prioritize, or act on them. This Skill reads those raw reports, converts them into a triaged action list, and applies only the fixes that are explicitly approved — without inventing fixes beyond what a report actually said. ## Core Features & Use Cases - Report collection and parsing: Reads every untriaged report.md under .ether/qa/jobs/ for a given target and extracts one action item per finding or follow-up line. - Severity-sorted action pipeline: Classifies each item as bug, warning, or note, with a summary, source reference, and proposed fix taken only from the report's own wording. - Gated fix application: Applies bug/warning fixes only after passing the ether job should-confirm autonomy gate, and records outcomes via ether job record-run so triage counts toward the job type's autonomy tier. - Use Case: After several local audit jobs have run, ask what the reviews found — the Skill presents a severity-ordered table of all findings, applies the fixes you approve, and marks each report as triaged so it is not reprocessed. ## Quick Start Ask the assistant to show what the QA job reports found and apply the approved fixes from the reports.

Frequently Asked Questions about qa-report-triage

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

FAQPage Schema
How do I review findings from local QA job reports?▼

Run the triage workflow, which reads every untriaged report.md under .ether/qa/jobs/ for your target and presents a severity-sorted table of bugs, warnings, and notes. Each item includes a summary, source reference, and any fix the report itself proposed.

How does the triage skill decide which fixes to apply automatically?▼

It checks the originating job type's autonomy tier via ether job should-confirm. At the confirm tier it presents the fix and waits for explicit user approval; at the autonomous tier it applies the fix directly. Only bug and warning items with concrete proposed fixes are candidates.

Does qa-report-triage work with repo-review-job or web-review-job reports?▼

No, those networked job types are not ported to this harness. The skill works with any local, offline job type built on the ether job router that writes findings to the .ether/qa/jobs/<jobId>/report.md convention.

Can the triage skill infer fixes for vague report findings?▼

No, it only acts on what a report explicitly states. Vague follow-ups or empty findings sections are surfaced as low-severity notes, and the skill asks the user rather than guessing at intent beyond the report text.

How does the skill avoid re-triaging the same report?▼

After processing, it appends a Triage section to the bottom of each report.md listing what was applied, skipped, or left pending. The collection step checks for this marker and skips already-triaged reports.