octo-issue-tracker
Skill1 starsChanged 6 months agoMITView on GitHub
Use this skill to triage GitHub issues — surface stale issues, propose labels, identify blockers, list PRs awaiting review, and draft responses. Triggers on "issues", "backlog", "triage", "PRs to review", "stale".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- steph-frtech/cdesign-expoword for word, first seen May 15, 2026
Other versions1 project uses a version of this.
Word for word · 1
- steph-frtech/cdesign-expo★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- .claude/marketplaces/superpowers/AGENTS.mdAGENTS.md
- .claude/marketplaces/superpowers/CLAUDE.mdCLAUDE.md
- .claude/marketplaces/wshobson/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- cavemanSkill
- improve-codebase-architectureSkill
- qaSkill
- zoom-outSkill
- scenario-testerSkill
- brainstormingSkill
- requesting-code-reviewSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- using-git-worktreesSkill
- writing-plansSkill
- exampleSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
When invoked, use the GitHub MCP server if available (fall back to gh issue list / gh pr list via Bash).
- Very specific: line 36
When scenario-tester requests issue creation for a failing test, create the entry here with a new OCTO-### ID and (if the GitHub MCP is …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
octo-issue-tracker — triage GitHub issues
You help track and triage GitHub issues for this project.
When invoked, use the GitHub MCP server if available (fall back to gh issue list / gh pr list via Bash). Then report:
- Stale issues — open for 30+ days with no activity. Suggest: close as stale, ping owner, or re-prioritize.
- Untriaged — issues with no labels and no assignee. Suggest concrete labels based on title/body.
- Blockers — labeled
blocker/release-blocker/ similar. Surface owner and current status. - PRs awaiting review — open >24h with no review activity. List reviewers who could unblock.
- Conflicting work — issues/PRs touching the same files (use GitHub's PR file lists).
For each item, propose one concrete next action (close, label, ping <user>, draft a response, request review from <user>). Never close issues or merge PRs without explicit user confirmation. Quote the issue/PR URL in every recommendation so the user can act in one click.
OCTO-### IDs
To cross-reference with the scenario-tester skill, maintain an .octo/ISSUES.md file at the repo root mapping each tracked issue to a stable local ID:
# OCTO Issues
## OCTO-001 — [bug] Payment retry double-debits
GitHub: https://github.com/owner/repo/issues/42
Status: open · Severity: high · Linked test: tests/scenarios/payment-flow.md#S4
## OCTO-002 — [feat] CSV import for users
GitHub: https://github.com/owner/repo/issues/57
Status: in-progress · Severity: mediumWhen scenario-tester requests issue creation for a failing test, create the entry here with a new OCTO-### ID and (if the GitHub MCP is configured) create the corresponding GitHub issue.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

