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

oss-maintainer-triage

Skill2 starsChanged 3 months agoMITView on GitHub

Triage open-source GitHub issues, pull requests, discussions, and maintenance backlogs. Use when converting maintainer queues into labels, priority, reproduction steps, owner decisions, review questions, release notes, or concrete next actions without over-promising fixes.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to help maintainers turn open-source project activity into clear, reviewable work.

    line 8
  2. Distinctive:

    Do not claim a bug is confirmed unless evidence shows it.

    line 25
  3. Distinctive:

    Avoid assigning severity without impact evidence.

    line 27
  4. Distinctive:

    Prefer common labels unless the repository has its own taxonomy:

    line 32

≈ “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

OSS Maintainer Triage

Use this skill to help maintainers turn open-source project activity into clear, reviewable work.

Workflow

  1. Gather the artifact under triage:
    • issue, PR, discussion, changelog, commit list, failing CI log, reproduction, or maintainer notes.
  2. Classify the work:
    • bug, feature, regression, docs, test, security, dependency, release, question, duplicate, needs reproduction, or wontfix.
  3. Identify maintainer action:
    • ask for information
    • reproduce locally
    • request tests
    • request design decision
    • review code
    • merge
    • close with reason
  4. Preserve uncertainty:
    • Do not claim a bug is confirmed unless evidence shows it.
    • Distinguish user reports from verified behavior.
    • Avoid assigning severity without impact evidence.
  5. Produce short, paste-ready maintainer output.

Suggested Labels

Prefer common labels unless the repository has its own taxonomy:

  • bug
  • enhancement
  • documentation
  • question
  • needs-reproduction
  • needs-tests
  • security
  • dependencies
  • release
  • good-first-issue

Output Format

Summary
- One sentence.

Suggested Labels
- label names

Maintainer Decision
- next action and why

Reply Draft
Short maintainer-facing response.

For PRs, include:

  • behavioral risk
  • missing tests
  • files likely needing review
  • merge/block recommendation

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