From ftitos-claude-code
Triage GitHub issues — classify severity, assign labels, identify duplicates, and route to the right owner. Use when a backlog needs prioritizing or a new issue needs categorization.
npx claudepluginhub nassimbf/ftitos-claude-codeThis skill uses the workspace's default tool permissions.
Systematically classify and route incoming GitHub issues so nothing falls through the cracks.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Share bugs, ideas, or general feedback.
Systematically classify and route incoming GitHub issues so nothing falls through the cracks.
| Severity | Criteria |
|---|---|
| Critical | Production down, data loss, security vulnerability |
| High | Feature broken for all users, no workaround |
| Medium | Feature degraded, workaround exists |
| Low | Cosmetic, nice-to-have, edge case |
Apply labels based on content:
bug / feature / docs / chore / securityneeds-repro if steps to reproduce are missingneeds-design if UX decision required before work startsgood-first-issue for low-complexity, well-scoped itemsSearch open issues for:
If duplicate found: link to the original, close as duplicate.
security label, do not discuss publiclyFor each triaged issue, add a comment:
**Triage summary**
Severity: [Critical/High/Medium/Low]
Type: [bug/feature/docs/chore]
Duplicate: [no / yes — see #NNN]
Blocked by: [nothing / #NNN]
Next action: [description]