메뉴
Classify a bug report, security finding, or feature request. Assigns priority P0-P3, picks a label, and creates a GitHub issue on the project board. Use whenever something needs to enter the backlog.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | triage |
| description | Classify a bug report, security finding, or feature request. Assigns priority P0-P3, picks a label, and creates a GitHub issue on the project board. Use whenever something needs to enter the backlog. |
| allowed-tools | Bash, Read |
Local setup:
gh issue create(GitHub) and Slack alerts need a remote + the Slack MCP, neither configured here. Locally, record the triage decision (priority, label, summary) in the conversation or a backlog note instead of opening an issue.
You convert raw inputs (bug descriptions, audit findings, feature ideas) into well-formed GitHub issues with priority, labels, and routing.
/triage bug: <description>
/triage feature: <description>
/triage security: <description>
/triage finding SC-F-1234 # Convert a scorecard finding into a GitHub issue
/triage from devops:<run-id> # Convert a CI failure into an issue
bug, feature, security, tech-debt, infra, docsarea:scorecards, area:auth, area:frontend, etc.), plus auto-triaged if generated by another skillneeds-owner label.gh issue create with the structured body below/notify to Slack #gatherly-alerts## Summary
<1-2 sentence problem description in user-facing terms>
## Context
<Why this matters, what's affected, who reported it>
## Steps to reproduce (bugs only)
1. ...
2. ...
## Expected
<What should happen>
## Actual
<What does happen>
## Acceptance Criteria
- [ ] AC-1 ...
- [ ] AC-2 ...
## Source
<Where this came from — user report, /audit-security run, /devops failure, /audit-service finding, etc.>
## Suggested approach
<Optional — if obvious, propose a direction. If not, leave blank.>
---
Auto-triaged by /triage on <timestamp>
Priority: P<N>
Owner: <team or unassigned>
Is the issue actively breaking production or leaking data?
├── YES → P0
└── NO →
Does it violate security (S1-S8) or break main branch?
├── YES → P1
└── NO →
Is it a real bug in a shipped feature, or HIGH-severity finding?
├── YES → P2
└── NO → P3
Sources that feed /triage:
| Source | Maps to |
|---|---|
/audit-security CRITICAL violation | P0 security |
/audit-security HIGH violation | P1 security |
/devops test failure on main | P1 bug |
/devops flaky test | P3 tech-debt |
/audit-service CRITICAL finding | P1 |
/audit-service HIGH finding | P2 |
/audit-service MEDIUM finding | P3 |
/review-pr HIGH bug | P2 |
gh issue list --search.Launch and drive the Gatherly app locally (FastAPI backend + Next.js frontend) and verify it renders. Use when asked to run, start, launch, or screenshot the app, or to confirm a change works in the real running app.
Scan code for security violations S1-S8 (auth, tenant isolation, RBAC, rate limiting, audit logging, raw SQL, secrets, HTTP timeouts). Use before commit on any code touching endpoints, services, or data access.
Run the event-readiness checklist against an event. Evaluates the readiness checks, produces findings, and routes them to the host. Use when the user asks to audit, score, or check the readiness of an event.
Commit changes with the dev-gatherly git identity using Conventional Commits format. Use after every atomic step in the REPL loop.
Push the current branch and create a production-ready PR with a complete description (What, Why, How to test). Runs /review-pr first if not already done. Use when implementation is complete.
Monitor CI/CD pipeline runs, diagnose failures, and route fixes to the right phase. Use after pushing a branch or when a pipeline turns red.