triage은(는) 무엇을 하나요?
트라이지 역할(triage roles)에 기반한 상태 머신(state machine)을 통해 이슈를 분류합니다. 사용자가 이슈를 생성하거나, 이슈를 분류하거나, 들어오는 버그 또는 기능 요청을 검토하거나, AFK 에이전트를 위해 이슈를 준비하거나, 이슈 워크플로우를 관리할 때 사용합니다.
이슈를 분류하는 상태 머신 기반 스킬입니다. 사용자가 이슈를 생성하거나, 트라이지(triage)를 수행하거나, 버그나 기능 요청을 검토하거나, AFK 에이전트를 위해 이슈를 준비하거나, 이슈 워크플로우를 관리할 때 사용합니다.
mattpocock/triage 스킬은 이슈 분류 작업을 상태 머신(state machine)을 기반으로 체계적으로 관리할 수 있게 해줍니다. 여러 트라이지 역할(예: 관리자, 리뷰어, 기여자)이 정의되어 있어, 이슈 상태를 '신규', '확인 중', '검토 필요', '해결 예정', '종료' 등으로 자동 전환하며 일관된 워크플로를 유지합니다. 주로 GitHub Issues 플랫폼에서 작동하며, 사용자는 간단한 명령어나 AI 에이전트를 통해 이슈 생성, 분류, 우선순위 지정, AFK(자리 비움) 에이전트에 전달, 종료까지 전체 프로세스를 효율적으로 처리할 수 있습니다. 개발자나 프로젝트 관리자에게 반복적이고 정형화된 이슈 관리 작업을 자동화하여 생산성을 높여줍니다.
npx skills add https://github.com/mattpocock/skills/tree/main/skills/triageInstalled? Explore more 생산성 & 협업 skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →
트라이지 역할(triage roles)에 기반한 상태 머신(state machine)을 통해 이슈를 분류합니다. 사용자가 이슈를 생성하거나, 이슈를 분류하거나, 들어오는 버그 또는 기능 요청을 검토하거나, AFK 에이전트를 위해 이슈를 준비하거나, 이슈 워크플로우를 관리할 때 사용합니다.
This repo contains 20 individual skills — each has its own dedicated page.
Ask which skill or flow fits your situation. A router over the skills in this repo.
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
Hand the current conversation off to a fresh background agent that picks up the work immediately.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft.
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Compact the current conversation into a handoff document for another agent to pick up.
Implement a piece of work based on a PRD or set of issues.
Implement a specification in code.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Grill me about specs for the workflows I want to build, within this workspace.
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian.
Gemini CLI one-shot prompts, summaries, generation, skills, hooks, MCP, or Gemma routing.
Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.
Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.
Search, install, update, sync, or publish agent skills with the ClawHub CLI and registry.
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
List, configure, authenticate, call, and inspect MCP servers/tools with mcporter over HTTP or stdio.