Claude-skill-registry issue-triage
Triage and analyze GitHub issues from iNavFlight/inav repository
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/issue-triage" ~/.claude/skills/majiayu000-claude-skill-registry-issue-triage && rm -rf "$T"
manifest:
skills/data/issue-triage/SKILL.mdsource content
GitHub Issue Triage Skill
Systematically analyze and categorize GitHub issues from the iNavFlight/inav repository.
File Structure
claude/manager/issue-triage/ INDEX.md # Quick lookup: issue# -> category file fetch_issues.py # Script to fetch and search issues issues.json # Cached issues data from GitHub readily-solvable.md # Issues ready to fix needs-investigation.md documentation.md enhancement-simple.md enhancement-complex.md hardware-dependent.md no-action.md # Won't fix, duplicates, already fixed
Quick Commands
Refresh Issue Cache
cd claude/manager/issue-triage python3 fetch_issues.py --refresh
Fetch More Issues
python3 fetch_issues.py --pages 5 --refresh
View Specific Issue
python3 fetch_issues.py --issue 11156
Search Issues
python3 fetch_issues.py --search "GPS" python3 fetch_issues.py --search "overflow"
List Cached Issues
python3 fetch_issues.py
Categories
| Category | File | Description |
|---|---|---|
| Readily Solvable | | Clear problem, known solution |
| Needs Investigation | | Promising, needs analysis |
| Documentation | | Docs fixes/improvements |
| Enhancement (Simple) | | Small feature additions |
| Enhancement (Complex) | | Major feature work |
| Hardware Dependent | | Needs specific hardware |
| No Action | | Won't fix, duplicates, etc. |
Workflow
- Refresh cache:
python3 fetch_issues.py --refresh - Review list for promising issues
- View details:
python3 fetch_issues.py --issue XXXXX - Add to INDEX.md with category link
- Add details to appropriate category file
Finding Readily Solvable Issues
Look for:
- Clear reproduction steps
- Isolated, specific problem
- No special hardware required
- Community consensus on behavior
- Small code changes
Avoid:
- Architecture changes needed
- Hardware-specific (can't test)
- Unclear requirements