Skip to content
Agentmart
Submit a tool

github-triage

Triage GitHub issues through a configurable label-based state machine.

Skill by OutlineDriven

IndexedApache-2.0★ 14
Write a review

Chalk Labs

Need help deploying github-triage?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/outlinedriven-github-triage

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Triage GitHub issues through a configurable label-based state machine. Use when user wants to triage incoming issues, prepare issues for an autonomous agent, or move an issue between workflow states. Repo inferred from `git remote`; all GitHub calls go through `gh`.

Use cases: productivity, agent-building

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/github-triage

What's inside

Skill name
github-triage
Description
Triage GitHub issues through a configurable label-based state machine. Use when user wants to triage incoming issues, prepare issues for an autonomous agent, or move an issue between workflow states. Repo inferred from `git remote`; all GitHub calls go through `gh`.
License
Apache-2.0
Instructions
91 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

State-machine triage over GitHub issues. Every comment posted carries an AI disclaimer. Label names are configurable; state semantics are not.

## AI disclaimer (mandatory)

Every comment or new issue body posted during triage MUST begin with:

```
> *This was generated by AI during triage.*
```

No exceptions.

## Label map (configure per project)

Bind ODIN's abstract state tokens to your repo's actual label names. Edit this block before first use; defaults match Matt Pocock's upstream convention.

```
category:
  bug:        "bug"             # something is broken
  enhancement:"enhancement"     # new feature or improvement
state:
  triage_pending:   "needs-triage"     # maintainer must evaluate
  awaiting_info:    "needs-info"       # waiting on reporter
  ready_for_agent:  "ready-for-agent"  # fully specified, autonomous-agent-suitable
  ready_for_human:  "ready-for-human"  # requires human judgment
  wont_fix:         "wontfix"          # closed, not actioned
```

Body uses the abstract tokens (`triage_pending`, `ready_for_agent`, etc.). Replace with your repo's labels at apply time.

## Invariants

- Every issue carries exactly one `category` label and one `state` label.
- Conflicting state labels = halt and ask the maintainer which is correct.
- Maintainer can override any state directly; flag unusual transitions.

## State machine

| From            | To                | Trigger             | Effect                                                                   |
| --------------- | ----------------- | ------------------- | ------------------------------------------------------------------------ |
| unlabeled       | triage_pending    | skill (first look)  | applies label after presenting recommendation                            |
| unlabeled       | ready_for_agent   | maintainer          | post agent brief, apply label                                            |
| unlabeled       | ready_for_human   | maintainer          | post task summary, apply label                                           |
| unlabeled       | wont_fix          | maintainer          | comment + close                                                          |
| triage_pending  | awaiting_info     | maintainer          | post triage notes capturing progress + reporter questions                |
| triage_pending  | ready_for_agent   | maintainer          | grilling complete; agent brief; apply label                              |
| triage_pending  | ready_for_human   | maintainer          | grilling complete; task summary; apply label                             |
| triage_pending  | wont_fix          | maintainer          | comment + close                                                          |
| awaiting_info   | triage_pending    | skill (reply seen)  | reporter replied; surface for re-evaluation                              |

## Workflows

### Overview ("what needs my attention")

Group open issues into three buckets and display oldest-first:

1. Unlabeled — never triaged.
2. `triage_pending` — needs evaluation or continuation.
3. `awaiting_info` with new activity since the last triage-notes comment.

### Triage a specific issue

1. Dispatch Explore agent to read full issue + all comments + related code paths.
2. Present category and state recommendations with reasoning.
3. For bugs: attempt reproduction. Run repo tests, trace logic.
4. If underspecified, run a `/domain-model` session.
5. Apply outcome per state.

## `awaiting_info` comment template

```markdown
## Triage Notes

**Established so far:**
- point 1
- point 2

**Need from you (@reporter):**
- specific question 1
- specific question 2
```

Reporter questions must be specific and actionable.

## Parallel examples

**TypeScript repo:** label-map binds `ready_for_agent → "agent-ready"`, `awaiting_info → "blocked-on-reporter"`. State machine and prose unchanged.

**Rust repo:** label-map binds `triage_pending → "S-needs-triage"`, `wont_fix → "C-wont-fix"` per Rust-project conventions. State machine and prose unchanged.

From OutlineDriven/odin-codex-plugin, Apache-2.0.

More from OutlineDriven/odin-codex-plugin

Signals

Stars
14
Forks
2
Open issues
2
Last commit (this folder)
Apr 28, 2026 (6 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from OutlineDriven

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get github-triage running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying github-triage?

CallGet help
Cite this page

github-triage skill. Agent Mart. https://agentmart.dev/skills/outlinedriven-github-triage (last updated 2026-10-24)