agentleFS
shuvamkshuvamk/openbench/.claude/skills/issue-triage/SKILL.md

issue-triage

Skill2 starsChanged 5 months agoApache-2.0View on GitHub

Reads open GitHub issues, applies/corrects the label taxonomy, flags stale or blocked ones, proposes status transitions. Use when the queue looks unhealthy or before planning a new milestone.

63 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use meeting-notes-and-actions, pr-review-ci-fix and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ComposioHQSkill

    meeting-notes-and-actions

    Turn meeting transcripts or rough notes into crisp summaries with decisions, risks, and owner-tagged action items; use for Zoom/Meet/Teams transcripts, call notes, or long meeting chats to generate share-ready outputs.

    Also in 4 projects that use this

  • ComposioHQSkill

    pr-review-ci-fix

    Automated PR review and CI auto-fix for GitHub and GitLab using the Composio CLI. Pulls diffs, fetches failing job logs, posts review comments, and loops fix commits until checks go green.

    Also in 4 projects that use this

  • FlorianBruniauxSkill

    tdd-rust

    Also in 3 projects that use this

  • GitHubSkill

    phoenix-cli

    Debug LLM applications using the Phoenix CLI. Fetch traces, analyze errors, structure trace review with open coding and axial coding, inspect datasets, review experiments, query annotation configs, and use the GraphQL API. Use whenever the user is analyzing traces or spans, investigating LLM/agent failures, deciding what to do after instrumenting an app, building failure taxonomies, choosing what evals to write, or asking "what's going wrong", "what kinds of mistakes", or "where do I focus" — even without naming a technique.

    Also in 3 projects that use this

  • petestewartSkill

    datadog-logs

    Query Datadog logs via the Logs Search API v2. Use when the user asks to "check the logs", "search logs", "find errors in Datadog", "look up logs for", "show me production logs", "check for errors", "search Datadog", or any request involving log search, error investigation, or production debugging that requires Datadog log data.

    Also in 3 projects that use this

  • +7 more from ComposioHQ

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the question is answerable by a reasonable autonomous call, answer it: make the call, log an ADR in .context/decisions.md, flip to …

    line 22

“Common” is measured: kept by at least 6 in 10 of the 51 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

issue-triage

The queue IS the coordination mechanism — a mislabeled issue is an agent deadlock.

Procedure

  1. gh issue list --state open --json number,title,labels,updatedAt,assignees --limit 200
  2. For each issue verify exactly one type:*, one area:*, one status:*, one p0|p1|p2 (taxonomy: .github/LABELS.md). Fix wrong/missing labels directly (gh issue edit --add-label/--remove-label) and comment one line explaining the correction.
  3. Staleness:
    • status:in-progress idle >36h → reap to status:ready, remove agent:claimed, un-assign, comment. (Nightly CI does this too — you're the manual pass.)
    • status:blocked → check the blocking issue; if closed, flip to status:ready.
    • status:needs-review with no open PR → back to status:in-progress or ready.
  4. status:needs-design audit: this label is ONLY for genuinely irreversible forks. If the question is answerable by a reasonable autonomous call, answer it: make the call, log an ADR in .context/decisions.md, flip to status:ready with a comment.
  5. Duplicates → close the newer with a link. Vague issues (no test-shaped acceptance criteria) → label agent:planned removed, comment what the planner must add.
  6. Report: one summary comment or output listing every transition made.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.