Issue Triage Loop
cobusgreyling/loop-engineering
Scans open GitHub issues and discussions, flags duplicates, scores priority and proposes labels into issue-triage-state.md without ever labeling or closing.
Triage an incoming GitHub, Jira, Linear, or other issue-tracker issue against the current codebase and related issues, then return a structured decision with exactly one triage state.
Install Triage
$ npx skills add bholmesdev/hubble.md --skill triage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bholmesdev/hubble.md triage --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/bholmesdev/hubble.md.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/triage .claude/skills/triage && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "triage" agent skill from https://github.com/bholmesdev/hubble.md/tree/main/.agents/skills/triage into .claude/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/bholmesdev/hubble.md/tree/main/.agents/skills/triageType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add bholmesdev/hubble.md --skill triage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bholmesdev/hubble.md triage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bholmesdev/hubble.md.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/triage .agents/skills/triage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "triage" agent skill from https://github.com/bholmesdev/hubble.md/tree/main/.agents/skills/triage into .agents/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bholmesdev/hubble.md --skill triage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bholmesdev/hubble.md triage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bholmesdev/hubble.md.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/triage .cursor/skills/triage && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "triage" agent skill from https://github.com/bholmesdev/hubble.md/tree/main/.agents/skills/triage into .cursor/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/bholmesdev/hubble.md.git --path .agents/skills/triage--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add bholmesdev/hubble.md --skill triage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bholmesdev/hubble.md triage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bholmesdev/hubble.md.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/triage .gemini/skills/triage && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "triage" agent skill from https://github.com/bholmesdev/hubble.md/tree/main/.agents/skills/triage into .gemini/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install bholmesdev/hubble.md triageInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add bholmesdev/hubble.md --skill triage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bholmesdev/hubble.md.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/triage .github/skills/triage && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "triage" agent skill from https://github.com/bholmesdev/hubble.md/tree/main/.agents/skills/triage into .github/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bholmesdev/hubble.md --skill triage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bholmesdev/hubble.md triage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bholmesdev/hubble.md.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/triage .opencode/skills/triage && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "triage" agent skill from https://github.com/bholmesdev/hubble.md/tree/main/.agents/skills/triage into .opencode/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
triage- GitHub stars
- 1.5k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 762 words
- Files
- 1
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- MIT
At a glance
Triage an incoming GitHub, Jira, Linear, or other issue-tracker issue against the current codebase and related issues, then return a structured decision with exactly one triage state.
- Works in 5 steps: Identify the issue and tracker → Fetch tracker context → Inspect the current codebase → …
- The user asks to triage
- SKILL.md covers Workflow and Guardrails
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Triage is an agent skill from bholmesdev/hubble.md. Triage an incoming GitHub, Jira, Linear, or other issue-tracker issue against the current codebase and related issues, then return a structured decision with exactly one triage state. Use whenever the user asks to triage, classify, assess, prioritize, or label an issue for implementation readiness, especially when an issue URL, key, or number is supplied in the prompt.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Issue triage. It works with GitHub and Jira. The repository describes itself as: The best notepad for you and your agents. The licence is MIT.
When your agent uses it
- The user asks to triage
- Label an issue for implementation readiness
- Especially when an issue URL
- Number is supplied in the prompt
Example prompts
- “/triage”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 571a523. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Triage loads about 1.5k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 762 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from bholmesdev/hubble.md at commit 571a523, republished under its MIT licence (© bholmesdev). 762 words, ~1,492 tokens.
Download SKILL.mdSave it as
.claude/skills/triage/SKILL.md (or your agent's skills folder).- name
- triage
- description
- Triage an incoming GitHub, Jira, Linear, or other issue-tracker issue against the current codebase and related issues, then return a structured decision with exactly one triage state. Use whenever the user asks to triage, classify, assess, prioritize, or label an issue for implementation readiness, especially when an issue URL, key, or number is supplied in the prompt.
Triage
Assess the issue passed in the user's prompt and decide exactly one triage state:
Ready to implementDuplicateNeeds discussion
The goal is to route work honestly, not to make every issue appear actionable. Base the decision on evidence from the issue tracker, current checkout, and related issues.
This is a read-only analysis: inspect the issue and codebase but do not mutate the tracker. Return the structured decision described in step 5; the caller applies the label and comment.
Workflow
1. Identify the issue and tracker
Extract the issue URL, key, or number from the prompt. Determine whether it belongs to GitHub Issues, Jira, Linear, or another tracker.
If the prompt does not identify one issue unambiguously, ask the user for the issue rather than guessing.
2. Fetch tracker context
Read the issue using the best available integration, in this order:
- A relevant MCP server or native tracker tool
- The tracker's authenticated CLI, such as
gh - The tracker's API or web page
Fetch:
- Full issue title and description
- Comments and discussion
- Existing labels, status, assignee, project, and linked issues
- Attachments or screenshots when they materially affect understanding
- The tracker's available labels
- Related open and closed issues, including likely duplicates, dependencies, and nearby product work
Do not classify solely from the title. Do not expose credentials or secrets while fetching tracker data.
3. Inspect the current codebase
Confirm the current checkout is the relevant repository. Search the codebase for the affected feature, behavior, terminology, and likely implementation area.
Assess:
- Whether the described behavior exists today
- Likely files, services, and systems involved
- Whether the issue has a bounded implementation path
- Dependencies, migrations, platform differences, and testing requirements
- Existing abstractions that make the change cohesive or indicate it does not fit
- Whether related issues or active work change the recommendation
Prefer targeted searches and reads. This is triage, not implementation: do not edit product code.
4. Choose one state
Use the following rubric. When evidence sits between states, choose Needs discussion.
Ready to implement
Choose when:
- Desired behavior and success criteria are clear
- Scope is bounded and cohesive with the current product
- Likely implementation area is identifiable
- Complexity and risk are low enough that an implementer (human or agent) has a good chance of completing it correctly in one pass
- No unresolved product decision or major dependency blocks implementation
Small bugs with clear reproduction steps and straightforward improvements usually belong here.
Duplicate
Choose when another issue already tracks the same underlying behavior and scope. Require concrete tracker evidence; similar symptoms or overlapping implementation areas alone are not enough.
- Identify the canonical issue in the comment
- Prefer the issue with clearer acceptance criteria, more discussion, or active implementation
- If the canonical issue was closed as fixed but the behavior recurs, verify it is not a regression before choosing
Duplicate - Do not close or otherwise mutate the issue; the caller owns tracker changes
Show full SKILL.md (280 more words)Show less
Needs discussion
Choose when neither implementation nor duplicate status is clear:
- Material product or technical decisions remain open
- Multiple valid designs, broad surface-area changes, or non-trivial dependencies make one-shot implementation risky
- The expected behavior, problem, scope, or reproduction is ambiguous
- Critical environment details, evidence, or acceptance criteria are missing
- The request may not fit the current product direction, conflicts with planned work, or a dependency makes it premature
5. Return the result
Pick the tracker label that matches the chosen state, preferring an existing label with the same meaning and the tracker's established naming and casing (for example ready-to-implement, needs-discussion, or duplicate).
Return a single raw JSON object as your final response — no prose and no markdown code fences:
{
"state": "Ready to implement | Duplicate | Needs discussion",
"label": "exact tracker label matching the chosen state",
"duplicate_of": "canonical issue URL or tracker key when state is Duplicate; otherwise null",
"comment": "markdown body for the issue"
}Write comment as reporter-facing markdown: a short lead sentence with the decision, then the evidence-based rationale, using a brief bullet list where it aids readability. For Needs discussion, end with the concrete questions and open decisions from step 4. For Duplicate, lead with Duplicate of <duplicate_of>, using the exact duplicate_of value from the result, and briefly state why it covers this report. Because comment is a JSON string, encode every line break as \n (a literal newline would make the JSON invalid).
Guardrails
- Do not mutate the tracker: no comments, labels, status, assignment, or other changes. Return the structured result instead.
- Do not implement the issue during triage or edit product code.
- Do not classify an issue without checking both the tracker context and the current codebase.
- Do not put raw secrets, tokens, private environment variables, command output dumps, or internal reasoning in the result.
- Treat comments from maintainers and linked product/spec documents as stronger evidence than guesses from code alone.
© bholmesdev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/triage of bholmesdev/hubble.md.
Open the folder on GitHubat commit 571a523
Compare with similar skills
Triage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Triage this skillbholmesdev/hubble.md | 1.5k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Issue Triage Loopcobusgreyling/loop-engineering | 11k | — | ~522 | Automated safety check: Pass | MIT | |
| Specwarpdotdev-demos/cloud-factory-demo | 320 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Triage Findingvlinx-io/VelaTerm | 259 | — | ~6.9k | Automated safety check: Pass | MIT | |
| Triagewarpdotdev-demos/cloud-factory-demo | 320 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Mfs Findzilliztech/mfs | 150 | — | ~4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Spec
warpdotdev-demos/cloud-factory-demo
Coordinate spec-driven development for a GitHub, Jira, Linear, or other issue-tracker issue marked ready-to-spec by using write-product-spec and write-tech-spec, creating PRODUCT.md and TECH.md…
Triage Finding
vlinx-io/VelaTerm
A skill your agent uses when the user supplies or imports existing security findings, vulnerability reports, or security/vulnerability Jira/Linear tickets from scanners, advisories, GitHub…
Triage
warpdotdev-demos/cloud-factory-demo
Triage an incoming GitHub, Jira, Linear, or other issue-tracker issue against the current codebase and related open issues, then return a structured decision with exactly one…
Mfs Find
zilliztech/mfs
Search, grep, browse, and read across registered MFS data sources via the mfs CLI — codebases, docs, PDFs, web crawls, databases (postgres/mysql/mongo/snowflake/bigquery), issue trackers…
Implementation
warpdotdev-demos/cloud-factory-demo
Implement a fix or feature from a GitHub, Jira, Linear, or other issue-tracker issue by fetching issue context, inspecting the current codebase, making code changes, validating them, verifying…
More from bholmesdev/hubble.md
All 13 skills in this repoChangelog
bholmesdev/hubble.md
Add a user-facing entry to CHANGELOG.md for work that just landed.
Review PR
bholmesdev/hubble.md
Review a pull request or local branch diff for correctness, security, lifecycle, error handling, tests, and meaningful performance risks.
Simplify
bholmesdev/hubble.md
Use this skill automatically when you feel your code is ready for human review, and whenever writing or reviewing code comments.
Write Product Spec
bholmesdev/hubble.md
Write a PRODUCT.md spec for a significant Hubble user-facing feature, focused only on user experience and observable behavior.
Write Tech Spec
bholmesdev/hubble.md
Write a TECH.md spec for a significant Hubble feature after researching the monorepo architecture.
Taste Review
bholmesdev/hubble.md
Ask Claude Code to make a taste-driven call on something ambiguous — UI polish, prose phrasing, naming, formatting.
Related
Categories
Questions about Triage
What does Triage do?
Triage an incoming GitHub, Jira, Linear, or other issue-tracker issue against the current codebase and related issues, then return a structured decision with exactly one triage state. md. Triage an incoming GitHub, Jira, Linear, or other issue-tracker issue against the current codebase and related issues, then return a structured decision with exactly one triage state.
When should I use Triage?
Triage fits situations like: the user asks to triage; label an issue for implementation readiness; especially when an issue URL; number is supplied in the prompt.
How do I install Triage in Claude Code?
Run `npx skills add bholmesdev/hubble.md --skill triage -a claude-code`. Or copy the skill folder (.agents/skills/triage in bholmesdev/hubble.md) into .claude/skills/triage in your project. Claude Code loads it when a task matches its description.
How do I install Triage in Codex?
Run `npx skills add bholmesdev/hubble.md --skill triage -a codex`. Or copy the skill folder (.agents/skills/triage in bholmesdev/hubble.md) into .agents/skills/triage in your project. Codex loads it when a task matches its description.
Can I use Triage in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bholmesdev/hubble.md --skill triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/triage, .gemini/skills/triage, .github/skills/triage and .opencode/skills/triage in your project.
What does Triage need to run?
SKILL.md names no scripts, command-line tools or credentials: Triage is instructions for the agent only.
Does Triage access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Triage safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Triage use?
Triage is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Triage use?
About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Triage?
Skills that share tags, products or a category with Triage: Issue Triage Loop (cobusgreyling/loop-engineering, 11k stars), Spec (warpdotdev-demos/cloud-factory-demo, 320 stars), Triage Finding (vlinx-io/VelaTerm, 259 stars) and Triage (warpdotdev-demos/cloud-factory-demo, 320 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Triage?
bholmesdev (a GitHub user) maintains it in bholmesdev/hubble.md, which has 1,483 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 1, 2026.
Source: bholmesdev/hubble.md on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.