agentleFS
railwayapprailwayapp/railpack/.agents/skills/triage-github-issues/SKILL.md

triage-github-issues

Skill1.3k starsChanged 32 days agoMITView on GitHub

Review open GitHub issues on the upstream repository and apply `bug`, `feature`, and `waiting-on-response` labels. Use when asked to triage, review, or label open GitHub issues.

1 other project uses a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 2 mentionsJan 2026: 5 mentionsFeb 2026: 2 mentionsMar 2026: 1 mentionApr 2026: 1 mentionMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 1 mentionAug 2026: 7 mentionsSep 2026: 8 mentionsOct 2026: 12 mentionsNov 2026: 4 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the railwayapp/railpack repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about railwayapp/railpack

The biggest 5 of 49 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 49

Talked about on GitHub and Hacker News (49 times).

On GitHub · 48

43 more on GitHub

On Hacker News · 1

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. google/skills_lint.dart★ 8same name

    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 repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Verify or create bug, feature, and waiting-on-response on railwayapp/railpack:

    line 13
  2. Very specific:

    Add waiting-on-response when a maintainer or collaborator has asked the issue author/user for clarifying information, their specific use …

    line 32
  3. Very specific:

    Do not add waiting-on-response if the user is the one asking a question waiting on a maintainer response, or if a maintainer merely invited …

    line 33
  4. Very specific:

    If an issue already has waiting-on-response and the user has since replied with the requested details, remove waiting-on-response.

    line 34
  5. Distinctive:

    Add labels to each issue:

    line 37
  6. Very specific:

    Remove stale waiting-on-response labels when answered:

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 and Label GitHub Issues

Review all open issues on railwayapp/railpack and apply bug, feature, and waiting-on-response labels based on issue descriptions and comment threads.

Instructions

  1. Ensure Required Labels Exist:
    • Verify or create bug, feature, and waiting-on-response on railwayapp/railpack:
      gh label create bug --repo railwayapp/railpack --description "Something isn't working" --color d73a4a 2>/dev/null || true
      gh label create feature --repo railwayapp/railpack --description "New feature or request" --color a2eeef 2>/dev/null || true
      gh label create waiting-on-response --repo railwayapp/railpack --description "Waiting on feedback/information from a user" --color fbca04 2>/dev/null || true
  2. Fetch Open Issues:
    • Query all open issues with their bodies, authors, existing labels, and full comment threads:
      gh issue list --repo railwayapp/railpack --state open --limit 200 \
        --json number,title,body,author,comments,labels,url
  3. Classify Each Issue:
    • Type (bug vs feature):
      • bug: Broken builds or runtime behavior, regressions, crashes, path/platform defects, inaccurate tool/version resolution, or unintended side effects in existing providers.
      • feature: Requests for new capabilities, support for additional package managers/languages/frameworks, new railpack.json schema options, or CLI/output enhancements.
    • Response Status (waiting-on-response):
      • Add waiting-on-response when a maintainer or collaborator has asked the issue author/user for clarifying information, their specific use case, a reproduction repository, or confirmation on whether a fix works, and the user has not yet replied with that information.
      • Do not add waiting-on-response if the user is the one asking a question waiting on a maintainer response, or if a maintainer merely invited a pull request without blocking on missing information.
      • If an issue already has waiting-on-response and the user has since replied with the requested details, remove waiting-on-response.
  4. Apply Label Updates:
    • Add labels to each issue:
      gh issue edit <number> --repo railwayapp/railpack --add-label "<label1>,<label2>"
    • Remove stale waiting-on-response labels when answered:
      gh issue edit <number> --repo railwayapp/railpack --remove-label "waiting-on-response"
  5. Report Summary:
    • Output a markdown table listing:
      • Issue number (linked) and title
      • Applied type (bug / feature)
      • waiting-on-response status
      • Concise 1-sentence rationale

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.