agentleFS
Sign inStart free
Dafenxz0Dafenxz0/codex-maintainer-skills/triage-oss-issue/SKILL.md

triage-oss-issue

Skill2 starsChanged 5 months agoMITView on GitHub

Triage open-source GitHub issues into maintainer-ready summaries. Use when Codex is asked to inspect a bug report, feature request, support question, reproduction notes, logs, screenshots, or issue thread and produce severity, labels, missing information, duplicate/search hints, reproduction steps, and a concise maintainer response.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    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. Distinctive:

    Search the local repo for related docs, tests, error strings, APIs, and previous fixes before recommending labels.

    line 13
  2. Very specific:

    Read references/label-taxonomy.md when label selection is needed.

    line 14
  3. Distinctive:

    Use this shape unless the user asks otherwise:

    line 19
  4. Distinctive:

    Treat security-looking reports conservatively and recommend private disclosure when exploit details, credentials, tokens, or vulnerable …

    line 41
  5. Distinctive:

    Do not promise fixes or timelines.

    line 42
  6. Distinctive:

    Prefer asking for one precise missing artifact over a broad "please provide more info".

    line 43
  7. Distinctive:

    If reproduction is weak, propose the smallest reproduction request that would unblock debugging.

    line 44
  8. Distinctive:

    If the issue is likely a duplicate, give search terms and candidate files rather than asserting a duplicate without evidence.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

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

Triage OSS Issue

Workflow

  1. Classify the issue as bug, feature, docs, support, security, performance, or question.
  2. Extract environment details, affected versions, expected behavior, actual behavior, reproduction steps, logs, and linked issues.
  3. Identify missing information that blocks maintainer action.
  4. Search the local repo for related docs, tests, error strings, APIs, and previous fixes before recommending labels.
  5. Read references/label-taxonomy.md when label selection is needed.
  6. Produce a maintainer note with: summary, likely component, severity, confidence, labels, next action, and a response draft.

Output

Use this shape unless the user asks otherwise:

Summary:

Classification:

Severity:

Suggested labels:

Evidence:

Missing information:

Recommended next action:

Maintainer response draft:

Triage Rules

  • Treat security-looking reports conservatively and recommend private disclosure when exploit details, credentials, tokens, or vulnerable versions appear.
  • Do not promise fixes or timelines.
  • Prefer asking for one precise missing artifact over a broad "please provide more info".
  • If reproduction is weak, propose the smallest reproduction request that would unblock debugging.
  • If the issue is likely a duplicate, give search terms and candidate files rather than asserting a duplicate without evidence.

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