원클릭으로
github-issue-triage
// Triage GitHub issues: label by type/priority, ask for repro on bugs, close obvious duplicates with a link to the canonical thread.
// Triage GitHub issues: label by type/priority, ask for repro on bugs, close obvious duplicates with a link to the canonical thread.
| name | github-issue-triage |
| description | Triage GitHub issues: label by type/priority, ask for repro on bugs, close obvious duplicates with a link to the canonical thread. |
| version | 1.0.0 |
| metadata | {"hermes":{"tags":["github","oss","maintainer","triage","issues"]}} |
Triage incoming GitHub issues so a solo maintainer's inbox doesn't explode. This skill labels new issues, asks for reproduction steps when they're missing, and closes duplicates with a link to the canonical thread.
For every new issue in a repository:
bug, feature-request, docs, question, support, spam. Use the existing labels on the repo if they exist; don't invent new label names.priority-high. If it mentions a minor visual glitch or a "nice to have" → priority-low. Default → priority-medium.bug label without clear reproduction steps (steps, expected, actual, version), post a comment asking for them in plain language.spam label and close.Default trigger is the GitHub issues.opened webhook. Configure via hermes webhook list. For manual run on a single issue:
/github-issue-triage owner/repo#42
In your agent config or skill metadata:
github:
default_repo: "owner/repo"
labels:
bug: "bug"
feature: "enhancement"
docs: "documentation"
spam: "spam"
dup_search_days: 90
spam_threshold: 0.85
ask_repro_template: |
Thanks for opening this. To reproduce on our end, can you share:
- The version of {project} you're on
- Steps to reproduce (1, 2, 3...)
- What you expected vs what actually happened
- Your OS / runtime if relevant
This skill is mostly classification + pattern matching:
This skill works best with the triager personality. Together they handle ~80% of incoming issues without the maintainer touching a keyboard.
For full PR review (not just issues), see the pr-first-review skill.
The full GitHub Maintainer team ships as a 4-agent bundle. See crewclaw.com/use-cases/github-maintainer-team.
Write signal-driven first lines for cold outreach. Leads with a recent hire, product launch, podcast quote, or funding round. Avoids generic 'I noticed your company...' openers.
Daily diff of competitor landing pages — pricing changes, hero copy swaps, new features mentioned. Flags meaningful changes only.
First-pass GitHub PR review: OWASP Top 10, style violations, scope creep, breaking changes. Comments before the maintainer looks.
Pull Stripe + Mixpanel + GA4 once a week, compute MRR / churn / ARPU / activation, send a digest to Slack with anomalies flagged.