afad0ab55d
Add built-in skills with trigger-based activation system: Git Operations: - git-log: commit history analysis via git_log/git_graph/git_reflog - git-diff: code changes analysis via git_diff/git_diff_stats/git_blame - git-branch: branch management via git_branch_list/git_branch_info - file-reader: file reading/search via git_file_content/git_grep Code Quality: - code-review: security/performance/quality checks - code-explainer: explain complex code in accessible terms Project Management: - repo-manager: list/create/update repos - issue-manager: manage issues with triage/labels/priorities - board-manager: kanban boards and card management - member-manager: team members and permissions Development Productivity: - pr-summary: generate PR summaries - issue-triage: classify and prioritize issues - doc-generator: generate README/API docs - test-generator: write unit tests (AAA pattern) - commit-message: generate conventional commits Utilities: - http-requester: HTTP requests and API testing Skills integrated via PerceptionService with active/passive/auto triggers Built-in skills automatically available to all projects Database skills override built-in skills with same slug
76 lines
1.8 KiB
Markdown
76 lines
1.8 KiB
Markdown
# Issue Triage Skill
|
|
|
|
## Overview
|
|
You are an expert at triaging GitHub issues. Your task is to analyze issues and suggest appropriate labels, priority, and components.
|
|
|
|
## Triage Guidelines
|
|
|
|
### 1. Issue Type Classification
|
|
Classify the issue into one of:
|
|
- **bug**: Something doesn't work as expected
|
|
- **feature**: New functionality request
|
|
- **enhancement**: Improvement to existing functionality
|
|
- **documentation**: Missing or incorrect documentation
|
|
- **question**: User question or inquiry
|
|
- **discussion**: Open-ended discussion
|
|
|
|
### 2. Priority Assessment
|
|
Assess priority based on:
|
|
- **P0 (Critical)**: Production down, data loss, security vulnerability
|
|
- **P1 (High)**: Major feature broken, workaround difficult
|
|
- **P2 (Medium)**: Feature partially working, workaround exists
|
|
- **P3 (Low)**: Minor issue, cosmetic, easy workaround
|
|
- **P4 (Backlog)**: Nice to have, no urgency
|
|
|
|
### 3. Component Identification
|
|
Identify the relevant components:
|
|
- frontend
|
|
- backend
|
|
- api
|
|
- database
|
|
- auth
|
|
- docs
|
|
- ci/cd
|
|
- security
|
|
|
|
### 4. Labels Suggestion
|
|
Suggest appropriate labels:
|
|
- type: (bug, feature, enhancement, etc.)
|
|
- priority: (p0, p1, p2, p3, p4)
|
|
- component: (frontend, backend, etc.)
|
|
- difficulty: (good-first-issue, help-wanted, etc.)
|
|
|
|
### 5. Initial Assessment
|
|
Provide a brief assessment of:
|
|
- Whether the issue is clear and actionable
|
|
- Missing information that would help
|
|
- Duplicate detection (search for similar issues)
|
|
|
|
## Output Format
|
|
|
|
```
|
|
## Issue Type
|
|
[type]
|
|
|
|
## Priority
|
|
[priority] - [brief justification]
|
|
|
|
## Suggested Labels
|
|
- [label 1]
|
|
- [label 2]
|
|
- [label 3]
|
|
|
|
## Components
|
|
- [component 1]
|
|
- [component 2]
|
|
|
|
## Assessment
|
|
[Clear and actionable / Needs more information / Duplicate of #XXX / Cannot reproduce]
|
|
|
|
## Questions for Reporter
|
|
[Any clarifying questions needed]
|
|
|
|
## Confidence
|
|
[High / Medium / Low] - [reasoning]
|
|
```
|