GitHub Issue Triager

Classifies and validates incoming GitHub issues. Extracts reproduction steps, environment data, assigns priority labels, and flags missing information.

1. Purpose

Turn disorganized user bug reports into structured, actionable engineering tickets.

2. When to Use

Use this skill when:

• Triaging new repository issues.
• Classifying incoming tickets (Bug, Feature, Question, Documentation).
• Requesting missing environment details from issue authors.

3. When Not to Use

• Do not use to write code fixes; use minimal-bug-fix.
• Do not use to create PRs; use github-pr-creator.

4. Required Inputs

• issue_title: Title of the GitHub issue.
• issue_body: Description and details posted by user.

5. Missing-Input Behavior

1. If reproduction steps are missing in a bug report: draft polite inquiry requesting OS, version, and minimal reproducible example.

6. Procedure

Follow these numbered actions:

1. Action 1: Classify Issue Type
   • bug, feature, documentation, or support.
2. Action 2: Assess Severity & Priority
   • P0 (Outage / Security), P1 (Core broken), P2 (Edge case), P3 (Minor / Cosmetic).
3. Action 3: Extract Reproduction Steps
   • Check for: Steps, Expected, Actual, Logs.
4. Action 4: Suggest Next Engineering Step
   • E.g. "Assign to bug-reproducer" or "Request clarification".

7. Decision Rules

• If issue contains a crash traceback: assign label bug and extract the failing line.
• If issue contains sensitive credentials: immediately flag for author redaction.

8. Output Format

Emit the triage report using this template:

### Issue Triage: #[Number] [Title]

- **Type**: [bug | feature | documentation | support]
- **Priority**: [P0 | P1 | P2 | P3]
- **Suggested Labels**: `[comma-separated labels]`

#### Problem Summary
[1-2 sentences]

#### Reproduction Status
- [ ] Clear reproduction steps provided
- [ ] Environment / version specified
- [ ] Traceback / error log attached

#### Next Action
- [Immediate next engineering step]

9. Verification Checklist

• Priority accurately reflects impact.
• Missing information clearly identified.
• Actionable next step defined.

10. Common Failures and Recovery

11. Stop or Escalation Conditions

Stop and ask the user when:

• Issue reports an active unpatched zero-day vulnerability (escalate privately).

12. Examples

Example 1: Successful Execution

Input:

Title: App crashes on startup when PORT is not set
Body: When I run npm start without PORT in .env, it throws TypeError: port.trim is not a function.

Output:

### Issue Triage: App crashes on startup when PORT is not set

- **Type**: bug
- **Priority**: P2
- **Suggested Labels**: `bug`, `configuration`, `dx`

#### Problem Summary
Startup crash occurs when `PORT` environment variable is undefined due to calling `.trim()` on undefined.

#### Reproduction Status
- [x] Clear reproduction steps provided (`npm start` without `PORT`)
- [x] Traceback / error log attached (`port.trim is not a function`)

#### Next Action
- Apply default port fallback in `src/config.ts` using `minimal-bug-fix`.

Example 2: Ambiguous or Missing Input

Input:

Title: Doesn't work
Body: Broken.

Output:

### Issue Triage: Doesn't work

- **Type**: support / incomplete
- **Priority**: P3
- **Suggested Labels**: `needs-reproduction`

#### Problem Summary
User reports the tool does not work without providing error messages or context.

#### Next Action
- Post response asking: "Please provide the exact command run, the observed error output, and your operating system."

Example 3: Expected Final Output

Output:

### Issue Triage: Add Dark Mode Toggle

- **Type**: feature
- **Priority**: P3
- **Suggested Labels**: `enhancement`, `ui`