메뉴
Autonomous triage agent that reviews untriaged GitHub issues, classifies them by type/priority/size, detects duplicates, and applies labels. Triggers: "triage issues", "review new issues", "label issues", "triage the backlog".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Create and refine HEARTBEAT.md files for murmur — a CLI daemon that runs scheduled Claude prompts on a cron or interval schedule. Use this skill when the user wants to set up a recurring automated action (e.g., "monitor my GitHub issues", "check Hacker News for AI articles", "watch my endpoints", "send me a daily digest"). Guides the user through an interview, drafts the heartbeat prompt, tests it, and registers it with murmur's scheduler. Triggers: heartbeat, murmur, recurring task, scheduled action, cron, monitor, watch, automate, periodic check, scheduled prompt.
Expert code review of current git changes with a senior engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements.
Expert in designing and building autonomous AI agents. Masters tool use, memory systems, planning strategies, and multi-agent orchestration. Use when: build agent, AI agent, autonomous agent, tool use, function calling.
Conduct enterprise-grade research with multi-source synthesis, citation tracking, and verification. Use when user needs comprehensive analysis requiring 10+ sources, verified claims, or comparison of approaches. Triggers include "deep research", "comprehensive analysis", "research report", "compare X vs Y", or "analyze trends". Do NOT use for simple lookups, debugging, or questions answerable with 1-2 searches.
Comprehensive guide to Effect-TS patterns for building robust TypeScript applications. Use when: (1) Writing Effect-TS code - effects, streams, layers, services, (2) Handling errors with typed errors and recovery, (3) Managing concurrency with fibers, queues, deferred, (4) Working with Schema for validation, (5) Building APIs or data pipelines, (6) Managing resources safely, (7) Understanding Effect fundamentals vs Promise/async-await. Triggers: "Effect", "effect-ts", "Effect.gen", "Effect.runPromise", "Schema", "Layer", "Service", "fiber", "Deferred", "Stream", "Chunk", "Option", "Either", "typed errors".
Designs system architecture, selects tech stacks, defines components and interfaces, addresses non-functional requirements. Trigger words - architecture, system design, tech stack, components, scalability, security, API design, data model, NFR, patterns, microservices, monolith
| name | triage-issues |
| description | Autonomous triage agent that reviews untriaged GitHub issues, classifies them by type/priority/size, detects duplicates, and applies labels. Triggers: "triage issues", "review new issues", "label issues", "triage the backlog". |
Autonomous workflow: fetch untriaged GitHub issues, classify each by type/priority/size, detect duplicates, and apply labels so the work-on-issues skill can pick them up.
gh CLI authenticated with repo accesstriaged, needs-info, security, duplicate, auto-dismissed, wontfix, in-progresspriority:must, priority:should, priority:couldsize:xs, size:s, size:m, size:l, size:xlCreate all required labels idempotently. Run each command — --force updates existing labels without error:
gh label create "triaged" --description "Issue has been triaged" --color "0E8A16" --force
gh label create "needs-info" --description "Needs more information from reporter" --color "D93F0B" --force
gh label create "security" --description "Security-related issue" --color "B60205" --force
gh label create "duplicate" --description "Duplicate of another issue" --color "CFD3D7" --force
gh label create "auto-dismissed" --description "Dismissed by triage agent" --color "CFD3D7" --force
gh label create "bug" --description "Something isn't working" --color "D73A4A" --force
gh label create "enhancement" --description "New feature or request" --color "A2EEEF" --force
gh label create "documentation" --description "Documentation improvements" --color "0075CA" --force
gh label create "question" --description "Further information requested" --color "D876E3" --force
gh label create "priority:must" --description "Critical — security, data loss, crashes, blocks core functionality" --color "B60205" --force
gh label create "priority:should" --description "Important — degrades UX, violates docs, affects common workflows" --color "FBCA04" --force
gh label create "priority:could" --description "Nice-to-have — cosmetic, edge cases, documentation polish" --color "C5DEF5" --force
gh label create "size:xs" --description "<20 lines, 1-2 files, trivial" --color "EDEDED" --force
gh label create "size:s" --description "20-100 lines, 1-3 files, straightforward" --color "D4C5F9" --force
gh label create "size:m" --description "100-300 lines, 3-6 files, needs new tests" --color "BFD4F2" --force
gh label create "size:l" --description "300-800 lines, 5-10 files, significant" --color "1D76DB" --force
gh label create "size:xl" --description "800+ lines, 10+ files, multi-day" --color "0052CC" --force
gh issue list --state open --json number,title,labels,body,comments,createdAt --limit 50
Filter out any issue that already has one of these labels: triaged, in-progress, duplicate, wontfix, auto-dismissed, needs-info.
If no untriaged issues remain, stop and report: "No untriaged issues found."
Process issues from oldest to newest. For each issue:
Fetch the full issue body and all comments:
gh issue view <NUMBER> --json body,comments,title,labels,createdAt
Read any files in the codebase referenced by the issue. Understand the context, what area of the project it affects, and how it relates to existing code.
Fetch all open and recently closed issues for comparison:
gh issue list --state all --json number,title,labels,state,body --limit 100
Compare the current issue against others by title similarity and body overlap. Only mark as duplicate if you are confident the issues describe the same problem or request — when in doubt, do not mark as duplicate.
If duplicate found:
duplicate, triagedgh issue edit <NUMBER> --add-label "duplicate,triaged"
gh issue comment <NUMBER> --body "<duplicate comment>"
gh issue close <NUMBER>
Then skip to the next issue.
Determine the issue's type, priority, and size using the rubrics below.
Type:
| Type | Criteria |
|---|---|
bug | Something is broken or behaves incorrectly |
enhancement | New feature or improvement to existing functionality |
documentation | Docs are missing, incorrect, or could be improved |
question | User is asking for help or clarification |
security | Security vulnerability or concern |
Priority:
| Label | Criteria |
|---|---|
priority:must | Security issues, data loss, crashes, breaks core scheduling/heartbeat execution |
priority:should | Degrades UX noticeably, violates documented behavior, affects common workflows |
priority:could | Nice-to-have, cosmetic, edge cases, documentation polish |
Size:
| Label | Criteria |
|---|---|
size:xs | <20 lines changed, 1-2 files, trivial fix |
size:s | 20-100 lines, 1-3 files, straightforward |
size:m | 100-300 lines, 3-6 files, needs new tests |
size:l | 300-800 lines, 5-10 files, significant |
size:xl | 800+ lines, 10+ files, multi-day effort |
needs-info + triaged, comment asking specific questions about what's missing. Do not classify priority/size.auto-dismissed + triaged, close the issue.security + priority:must + appropriate size + triaged. Add a note in the comment flagging it for human review.Apply the classification labels and leave a triage summary comment.
gh issue edit <NUMBER> --add-label "<type>,priority:<level>,size:<size>,triaged"
gh issue comment <NUMBER> --body "<triage comment>"
Standard triage:
## Triage
| Priority | Size |
| -------- | ------ |
| <LEVEL> | <SIZE> |
**Summary:** <Brief 1-2 sentence classification of the issue and what it involves.>
---
_Auto-triaged by murmur_
Duplicate:
**Duplicate of #<NUMBER>**
This appears to duplicate #<NUMBER>. Tracking progress there.
---
_Auto-triaged by murmur_
Needs more information:
## Needs More Information
<Specific questions about what's missing or unclear.>
---
_Auto-triaged by murmur_
Security:
## Triage
| Priority | Size |
| -------- | ------ |
| MUST | <SIZE> |
**Summary:** <Brief classification.>
**Note:** This is a security-related issue and has been flagged for human review.
---
_Auto-triaged by murmur_
After processing all issues, output a summary of actions taken:
triaged label on every outcome (prevents re-processing on next run)good first issue or help wanted — those are for humans to assignin-progress — that's for work-on-issues when it claims an issuework-on-issues for implementation after triage is complete