triage

Point the agent at an issue identifier and it inspects the full request, replies, and prior triage notes. It verifies bug claims by reproducing them or reading the code, then recommends or applies the appropriate workflow state using the project's existing labels.

Reproduce the reported behavior or inspect the relevant code paths before applying any confirmation label. The Skill separates confirmed observations from assumptions and only asks reporters for information that blocks a reliable next step.

Yes, it resolves whether a supplied identifier names an issue or PR before acting. For pull requests it includes the diff in its review, describing what the diff already provides and the remaining gaps rather than requesting a full rebuild.

An implementation brief captures the request and evidence, current and desired behavior, relevant contracts and code pointers, acceptance criteria, and scope exclusions. It lets a fresh contributor verify and implement the request without reconstructing the original conversation.

Record a rejection only for explicit scope decisions, not for already-implemented behavior or merely deferred work. If the project maintains a decision record, match requests by concept and append to existing decisions rather than creating per-issue files.

No, an explicit state-change request authorizes only that specific change, not unrelated comments or closures. For read-only triage it reports the recommended state and evidence without modifying the tracker.