本文へ移動
cccskills
無料GitHub で公開

triage

Apply a formal state machine to issues — assign category (bug/enhancement/question/spike) and state (needs-triage → needs-info → ready-for-agent → ready-for-human → wontfix). Issues marked ready-for-agent become inputs to supergraph:plan. Use when processing a backlog, reviewing new issues, or preparing work for automation.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

/supergraph:triage

Classify issues with a formal state machine. ready-for-agent is the handoff trigger to the supergraph pipeline.

Announce: "🗂️ /supergraph:triage — classifying issues..."

State Machine

needs-triage
    ├── enough info → [assign category] → ready-for-agent | ready-for-human
    └── missing info → needs-info → [info provided] → ready-for-agent | ready-for-human

ready-for-agent  → supergraph:plan pipeline
ready-for-human  → manual dev / architectural decision needed
wontfix          → closed with reason

Category Roles

CategoryWhen
bugObserved behavior differs from specified behavior
enhancementNew capability or improvement to existing behavior
questionNeeds clarification before any action
spikeResearch / proof-of-concept, no production code

State Roles

StateMeaning
needs-triageUnreviewed — default for new issues
needs-infoBlocked on missing information from reporter
ready-for-agentFully specified — safe for /supergraph:plan to consume
ready-for-humanNeeds human judgment (architecture, business decision, security)
wontfixWill not be addressed — reason required

Triage Workflow

For each issue:

1. Read the issue completely.

2. Assign category — bug / enhancement / question / spike.

3. Check readiness for agent:

A bug is ready-for-agent when:

  • Steps to reproduce are clear
  • Expected vs actual behavior is stated
  • Environment info is present (version, OS, config)
  • No architectural decision required

An enhancement is ready-for-agent when:

  • Acceptance criteria are defined
  • Scope is bounded (not open-ended)
  • No design decision blocking implementation

If NOT ready → set needs-info and list exactly what's missing (one question per response).

4. Assign state and apply labels via GitHub CLI:

gh issue edit <number> --add-label "bug,needs-info"
gh issue edit <number> --add-label "enhancement,ready-for-agent"
gh issue edit <number> --add-label "wontfix"
# Add comment explaining state change:
gh issue comment <number> --body "Triage: [reason for state]"

5. For ready-for-agent issues — summarize for plan intake:

Issue #N: [title]
Category: bug | enhancement
Acceptance: [1-3 criteria]
Constraints: [any known]
→ /supergraph:plan

Batch Triage

For a backlog of issues:

gh issue list --state open --label "needs-triage" --json number,title,body

Process each in order. Report counts at end:

Triaged: N issues
  ready-for-agent: N  ← entry point for /supergraph:plan
  needs-info: N
  ready-for-human: N
  wontfix: N

Rules

  • Never mark ready-for-agent unless acceptance criteria are unambiguous
  • ready-for-human for anything requiring architecture, security, or business decisions
  • One question at a time for needs-info issues — don't dump all questions at once
  • wontfix always requires a reason in the comment

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

analyze

無料

Risk analysis and approach selection before planning. Use when requirements are ambiguous, approaches vary, or work touches hub/bridge nodes. Skip for typo fixes.

日本語の概要は準備中です。原文の説明を表示しています。

datit309/supergraph222026年10月11日 更新

Proactive architecture review — explore codebase structure, generate a self-contained HTML report with Mermaid diagrams and candidate improvements, then grill the findings. Use when planning a large refactor, onboarding to an unfamiliar codebase, or before a major architectural change.

日本語の概要は準備中です。原文の説明を表示しています。

datit309/supergraph222026年10月11日 更新

caveman

無料

Persistent token-compression mode (~75% reduction) — now always-on by default. Strips filler while keeping code exact.

日本語の概要は準備中です。原文の説明を表示しています。

datit309/supergraph222026年10月11日 更新

Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).

日本語の概要は準備中です。原文の説明を表示しています。

datit309/supergraph222026年10月11日 更新

Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

日本語の概要は準備中です。原文の説明を表示しています。

datit309/supergraph222026年10月11日 更新

diagnose

無料

Structured 6-phase debugging. Build feedback loop first, reproduce deterministically, hypothesize with ranked falsifiable theories, instrument one variable at a time, fix with regression test, cleanup. Use when a bug exists, tests fail unexpectedly, or behavior is wrong and cause is unknown.

日本語の概要は準備中です。原文の説明を表示しています。

datit309/supergraph222026年10月11日 更新

datit309 のスキルをすべて見る

このスキルの問題を報告する