agentleFS
Sign inStart free
ric03uecric03uec/clawrium/skills/hermes/issue-triage/SKILL.md

issue-triage

Skill67 starsChanged 2 months agoApache-2.0View on GitHub

Triage new and updated GitHub issues on ric03uec/clawrium — apply type/complexity/area labels and draft a planning file.

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

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 1

    Distinctive

    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
  1. Very specific:

    If the issue body is empty or one sentence, label needs-review and leave a single short comment asking for Outcome + Definition of Done.

    line 53
  2. Distinctive:

    Do not invent requirements.

    line 55
  3. Very specific:

    If LABELS.md is missing or unreadable, stop and post a [ITX-STUCK] comment on the issue rather than guessing label names.

    line 56

“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

Triage incoming work on ric03uec/clawrium. Run on a 10-minute poll cycle. The loop is: find issues that need triage → read them carefully → apply labels → draft a planning file as a PR.

Inputs

For each candidate issue:

  • Title and body.
  • Current labels (skip if needs-triage is absent or the issue already has a type:* label).
  • The repo's LABELS.md for the allowed taxonomy. Do not invent labels.

Candidates are issues opened or updated in the last 15 minutes (giving the poll a 5-minute overlap so nothing is missed during a slow run). Use:

gh issue list --repo ric03uec/clawrium \
  --search "sort:updated-desc updated:>$(date -u -d '15 minutes ago' +%Y-%m-%dT%H:%M:%SZ)" \
  --json number,title,body,labels,updatedAt

Output

  • Apply labels from the taxonomy in LABELS.md. At minimum: one type:*, one complexity:*, one area:*. Add needs-review when the issue lacks a clear Definition of Done.
  • Open a PR adding .itx/active/<issue-number>/plan.md with a one-page scaffold (Outcome / Approach / Files / Risk). Title: chore(triage): draft plan for #<n>. Body links to the issue.

Hard constraints

  • Never apply the agent-ready label. The PAT denies it; even if it did not, this label is a human decision.
  • Never push directly to main or merge a PR. PRs target main with a feature branch named triage/<issue-number>-<slug>.
  • If the issue body is empty or one sentence, label needs-review and leave a single short comment asking for Outcome + Definition of Done. Do not invent requirements.
  • If LABELS.md is missing or unreadable, stop and post a [ITX-STUCK] comment on the issue rather than guessing label names.

Anti-patterns

  • Re-labeling issues that already have a type:* label — assume a human or earlier triage decided. Touch only the missing dimensions.
  • Drafting an .itx/active/<n>/plan.md that exceeds one page. The plan is a starting point for /itx-plan-create, not a substitute for it.
  • Commenting on the issue with summaries of the body. The body is the source of truth; do not paraphrase it back.

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.

Check your setup, free