triage-feedback

Triages GitHub Project feedback issues into Not planned, fold-in, or Backlog verdicts.

3|3|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/PioneerAIAcademy/cowork-genealogy --skill triage-feedback-pioneeraiacademy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage-feedback
Source: https://github.com/PioneerAIAcademy/cowork-genealogy/tree/main/.claude/skills/triage-feedback
Command: npx skills add https://github.com/PioneerAIAcademy/cowork-genealogy --skill triage-feedback-pioneeraiacademy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Alpha tester feedback piles up in a GitHub Project Feedback column with no owner, and raw submissions are titled with timestamps rather than actionable descriptions. This Skill works that queue one item at a time, verifying each claim against the repository before any issue is filed, so duplicate or misdiagnosed work never reaches the backlog. ## Core Features & Use Cases - Claim Verification: Separates what the tester observed from what they concluded, then confirms, refutes, or flags each claim as unverifiable with cited file paths. - Duplicate Detection: Searches open issues by fix site before reading code, folding new evidence into existing issues instead of creating duplicates. - Backlog Issue Authoring: Retitles timestamp-stamped submissions and writes instructions with Touches lines, verified evidence, concrete approach, and explicit out-of-scope notes. - Use Case: A tester reports that a feature is missing. The Skill finds the feature working in the repo, identifies the genuinely broken project state underneath the wrong diagnosis, and files a Backlog issue targeting the real problem. ## Quick Start Ask the agent to triage the feedback column on the project board and work through the untriaged items one at a time.

Frequently Asked Questions about triage-feedback

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

FAQPage Schema
How do I triage user feedback issues on a GitHub Project board?▼

List items in the Feedback column with gh project item-list, read each issue body, verify claims against the repository, then close as not planned, fold into an existing issue, or move to Backlog with written instructions. Work one item at a time, oldest first.

How to avoid filing duplicate GitHub issues from user feedback?▼

Search open issues by fix site rather than symptom before reading any code, using gh issue list with a search query. Issues that collide rarely share titles, so read the Touches lines to find items targeting the same files.

Can this Skill edit code or open pull requests?▼

No. It is deliberately restricted to Read, Bash, Glob, and Grep with no Edit or Write tool. It proposes verdicts and applies only what the lead approves, and it never starts the work it scopes.

Why does gh project item-list report a rate limit when the API shows quota remaining?▼

The full-board read consumes the GraphQL points budget, not the hourly request window, so gh api rate_limit can still show 5000 of 5000. The budget clears in minutes; run the board read once per session and use single-card queries afterward.

What happens if the feedback label is left on a Backlog item?▼

The label means untriaged, so the downstream fill-ready skill reads the item as a triage slip and refuses to promote it. Removing the feedback label when moving a card to Backlog is a required step, not optional.