triage-new-issues

Included with Lifetime

$97 forever

Review new GitHub issues, assess priority and urgency, suggest labels, and recommend assignees

Code Reviewtriageissuesprioritylabelsbacklog

What this skill does


# Triage New Issues Skill

Review new or untriaged GitHub issues, assess priority based on urgency signals, suggest labels, and recommend owners.

## When to Use

Activate when:
- Processing new incoming issues
- Reviewing untriaged backlog
- Assessing issue priority
- Assigning issues to owners

## Output Structure (per issue)

```markdown
## Triage: #[number] — [title]

### Priority Assessment

**Urgency**: [Critical | High | Medium | Low]
**Impact**: [Wide | Moderate | Limited]
**Recommended Priority**: P[0-3]

| Signal | Indicator |
|--------|-----------|
| [Keyword/label found] | [What it suggests] |

### Classification

**Type**: [Bug | Feature | Question | Task]
**Area**: [Component or area affected]
**Suggested Labels**: `priority/high`, `bug`, `area/auth`
**Suggested Assignee**: @username (owns this area)

### Assessment

[Summary of the issue and reasoning for priority assignment]

### Clarifying Questions (if needed)

- [ ] [Question to understand severity]

### Recommendation

[Immediate action | Next sprint | Backlog | Needs info | Duplicate of #X]
```

## Priority Signals

### Critical (P0)
**Keywords**: "down", "outage", "security", "vulnerability", "production", "urgent", "ASAP", "breach"
**Labels**: `critical`, `security`, `production`
**Action**: Immediate attention required

### High (P1)
**Keywords**: "blocking", "regression", "broken", "can't use", "data loss", "crash"
**Labels**: `blocker`, `regression`, `priority/high`
**Action**: Address this sprint

### Medium (P2)
**Keywords**: "bug", "incorrect", "should", "expected", "wrong"
**Labels**: `bug`, `priority/medium`
**Action**: Schedule for upcoming sprint

### Low (P3)
**Keywords**: "nice to have", "minor", "cosmetic", "enhancement", "workaround exists"
**Labels**: `enhancement`, `low-priority`
**Action**: Add to backlog

## Triage Guidelines

### Assessment Process

1. Read title and full description
2. Scan for urgency keywords and labels
3. Check for existing labels that signal priority
4. Assess impact (how many users affected)
5. Look for workarounds mentioned
6. Check if duplicate of existing issue

### When to Escalate

- Security vulnerabilities → Flag immediately
- Production outages → Notify on-call
- Data integrity issues → High priority regardless of other signals

### When to Ask Questions

- Unclear reproduction steps
- Missing environment details
- Ambiguous severity ("it's broken" but unclear impact)
- No indication of urgency or timeline

### Red Flags

- Issues with no response from author (>7 days)
- Duplicate of closed/wontfix issue
- Feature request disguised as bug
- Missing required information from template

Files: 1

Size: 2.9 KB

Complexity: 10/100

Category: Code Review

Source: https://github.com/britt/claude-code-skills/tree/main/skills/triage-new-issues

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts