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
Most recently taken up by
- google/skills_lint.darttheir own version, first seen Oct 13, 2026
Who's talking about railwayapp/railpack
- A Hacker News story“Show HN: Railpack – Zero-Config Dockerimage Builds”Hacker News · Mar 4, 2025 · 6 points
- coollabsio/coolify“[Feature Request] Migrate from Nixpacks to Railpack - Nixpacks is in Maintenance Mode”GitHub · Jan 18, 2026 · 2 reactions
- coollabsio/coolify“[Bug]: Railpack ignores filtered `deploy.inputs` and slows deployments”GitHub · Sep 13, 2026 · 1 reactions
- Guillaume-Docquier/text-based-browser-game-1“project(pnpm): use devEngines.packageManager and remove stale nvmrc”GitHub · Aug 29, 2026 · 1 reactions
- Guillaume-Docquier/text-based-browser-game-1“project(pnpm): Restore devEngines.packageManager”GitHub · Aug 29, 2026 · 1 reactions
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
- Jan 18, 2026[Feature Request] Migrate from Nixpacks to Railpack - Nixpacks is in Maintenance Mode — coollabsio/coolify2 reactions · 2 comments
- Sep 13, 2026[Bug]: Railpack ignores filtered `deploy.inputs` and slows deployments — coollabsio/coolify1 reaction · 2 comments
- Aug 29, 2026project(pnpm): use devEngines.packageManager and remove stale nvmrc — Guillaume-Docquier/text-based-browser-game-11 reaction · 3 comments
- Aug 29, 2026project(pnpm): Restore devEngines.packageManager — Guillaume-Docquier/text-based-browser-game-11 reaction · 3 comments
- Nov 11, 2026build(ci): migrate action pinning from pinact to GitHub Actions lockfile — iloveitaly/python-starter-template0 reactions
43 more on GitHub
- Nov 11, 2026Bump the go group in /daemon with 10 updates — vantezzen/launchroom0 reactions · 1 comment
- Nov 4, 2026Bump the go group across 1 directory with 8 updates — vantezzen/launchroom0 reactions · 1 comment
- Nov 2, 2026feat(api): 階段 2 完整後端(多季 API、資料、寫入與安全) — abowchen2025/move-or-not0 reactions
- Oct 30, 2026chore: bump the go-deps group with 13 updates — glincker/levelrail0 reactions · 2 comments
- Oct 29, 2026chore(deps): bump github.com/railwayapp/railpack from 0.42.0 to 0.43.0 — leanhanc/tero0 reactions
- Oct 25, 2026Bump the go group across 1 directory with 5 updates — vantezzen/launchroom0 reactions · 2 comments
- Oct 23, 2026chore: bump the go-deps group with 7 updates — glincker/levelrail0 reactions · 5 comments
- Oct 22, 2026chore(deps): bump github.com/railwayapp/railpack from 0.40.1 to 0.42.0 — leanhanc/tero0 reactions · 1 comment
- Oct 20, 2026chore(deps): update module github.com/railwayapp/railpack to v0.43.0 - autoclosed — cubeshipd/cubeship0 reactions · 1 comment
- Oct 20, 2026chore(deps): update dependency railwayapp/railpack to v0.43.0 — hops-ops/hops-cli0 reactions · 1 comment
- Oct 16, 2026chore: pin GitHub Actions with a 30-day cooldown — iloveitaly/python-starter-template0 reactions
- Oct 16, 2026chore(deps): update dependency railwayapp/railpack to v0.42.0 — hops-ops/hops-cli0 reactions · 1 comment
- Oct 14, 2026chore(deps): update dependency railwayapp/railpack to v0.41.0 — hops-ops/hops-cli0 reactions · 2 comments
- Oct 12, 2026chore(deps): update module github.com/railwayapp/railpack to v0.42.0 — cubeshipd/cubeship0 reactions · 2 comments
- Oct 2, 2026chore: bump the go-deps group across 1 directory with 12 updates — glincker/levelrail0 reactions · 3 comments
- Sep 28, 2026chore(deps): update dependency railwayapp/railpack to v0.40.1 — hops-ops/hops-cli0 reactions · 1 comment
- Sep 28, 2026chore: bump the go-deps group across 1 directory with 11 updates — glincker/levelrail0 reactions · 8 comments
- Sep 25, 2026chore(deps): update dependency railwayapp/railpack to v0.40.0 — hops-ops/hops-cli0 reactions · 1 comment
- Sep 11, 2026chore(deps): update dependency railwayapp/railpack to v0.39.0 — hops-ops/hops-cli0 reactions · 1 comment
- Sep 11, 2026build(deps): bump github.com/railwayapp/railpack from 0.37.1 to 0.39.0 in the railpack group — nitrictech/sugapack0 reactions
- Sep 11, 2026chore: bump github.com/railwayapp/railpack from 0.38.0 to 0.39.0 — glincker/levelrail0 reactions · 2 comments
- Sep 4, 2026chore: bump github.com/railwayapp/railpack from 0.37.1 to 0.38.0 — glincker/levelrail0 reactions · 1 comment
- Aug 29, 2026Optimize backend deployment memory usage — Guillaume-Docquier/text-based-browser-game-10 reactions
- Aug 28, 2026chore: bump github.com/railwayapp/railpack from 0.36.4 to 0.37.1 — glincker/levelrail0 reactions · 1 comment
- Aug 28, 2026build(deps): bump github.com/railwayapp/railpack from 0.36.4 to 0.37.1 in the railpack group — nitrictech/sugapack0 reactions
- Aug 15, 2026feat: Railpack auto-detection for Node.js and Go builds — glincker/levelrail0 reactions · 1 comment
- Aug 1, 2026fix(spindrift): take the plan generator from the frontend it feeds — jonpulsifer/infra0 reactions · 1 comment
- Jul 25, 2026Manage pnpm via devEngines — Guillaume-Docquier/text-based-browser-game-10 reactions
- May 5, 2026references/deploy.md misleads about RAILPACK_STATIC_FILE_ROOT for Node SPA projects (caused production outage) — railwayapp/railway-skills0 reactions
- Apr 29, 2026Feat/add six language providers (#13) — usetheoai/theo-packs0 reactions
- Mar 23, 2026Update Railpack to 0.23.0 — PurdueRCAC/AnvilOps0 reactions
- Feb 25, 2026Nix buildpack — SwissDataScienceCenter/renku-frontend-buildpacks0 reactions
- Feb 16, 2026Update Railpack to 0.20.0 — PurdueRCAC/AnvilOps0 reactions
- Jan 26, 2026Update Railpack to 0.17.1 — PurdueRCAC/AnvilOps0 reactions
- Jan 19, 2026Update Railpack to 0.17.0 — PurdueRCAC/AnvilOps0 reactions
- Jan 5, 2026Migrate Railway deployments from Nixpacks to Railpack with explicit Node.js 20.19.0 configuration — JonSvitna/FitnessAPP0 reactions
- Jan 1, 2026[Request]: railpack — ScoopInstaller/Main0 reactions
- Dec 12, 2025chore(deps): update dependency ubi:railwayapp/railpack to v0.15.1 — homarr-labs/dashboard-icons0 reactions · 7 comments
- Dec 4, 2025chore(deps): update dependency ubi:railwayapp/railpack to v0.15.1 — homarr-labs/dashboard-icons0 reactions · 2 comments
- Aug 26, 2025Normalize compose commands when generating for heroku migration — DefangLabs/defang0 reactions
- Jul 2, 2025Railway — Mamonaminyar/mamon0 reactions
- Mar 31, 2025Ruby Gem — Milanhe92/Velika-masina0 reactions
- Mar 30, 2025Name: Remote - Tunnels Id: ms-vscode.remote-server Description: Connect to a remote machine through a Tunnel Version: 1.5.2 Publisher: Microsoft VS Marketplace Link: https://marketplace.visualstudio.com/items/?itemName=ms-vscode.remote-server — Milanhe92/Milan-He0 reactions · 1 comment
On Hacker News · 1
- Mar 4, 2025Show HN: Railpack – Zero-Config Dockerimage Builds6 points · 2 comments
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 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.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- reproduce-github-issueSkill
- retry-flakey-jobsSkill
- railpackSkill
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
- Very specific: line 13
Verify or create bug, feature, and waiting-on-response on railwayapp/railpack:
- Very specific: line 32
Add waiting-on-response when a maintainer or collaborator has asked the issue author/user for clarifying information, their specific use …
- Very specific: line 33
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 …
- Very specific: line 34
If an issue already has waiting-on-response and the user has since replied with the requested details, remove waiting-on-response.
- Distinctive: line 37
Add labels to each issue:
- Very specific: line 41
Remove stale waiting-on-response labels when answered:
≈ “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.
Files
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
- Ensure Required Labels Exist:
- Verify or create
bug,feature, andwaiting-on-responseonrailwayapp/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
- Verify or create
- 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
- Query all open issues with their bodies, authors, existing labels, and full comment threads:
- Classify Each Issue:
- Type (
bugvsfeature):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, newrailpack.jsonschema options, or CLI/output enhancements.
- Response Status (
waiting-on-response):- Add
waiting-on-responsewhen 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-responseif 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-responseand the user has since replied with the requested details, removewaiting-on-response.
- Add
- Type (
- Apply Label Updates:
- Add labels to each issue:
gh issue edit <number> --repo railwayapp/railpack --add-label "<label1>,<label2>" - Remove stale
waiting-on-responselabels when answered:gh issue edit <number> --repo railwayapp/railpack --remove-label "waiting-on-response"
- Add labels to each issue:
- Report Summary:
- Output a markdown table listing:
- Issue number (linked) and title
- Applied type (
bug/feature) waiting-on-responsestatus- Concise 1-sentence rationale
- Output a markdown table listing:
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
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.

