Agent skill · marketing growth · steipete
github-project-triage
GitHub issue/PR triage: queues, CI, blockers, risk, proof, next actions.
Why this skill is useful
Provides specific commands and workflows for triaging GitHub issues and PRs that enhance project management capabilities.
What it needs
Requires gh, swift installed locally. Requires github account access. About 9k tokens when loaded. Last updated 2026-08-06. 6,510 stars on the source repository.
What this skill does
GitHub Project Triage Always use this skill when the user types triage, unless the request explicitly targets a non-GitHub domain. From inside a repo, use the current GitHub project by default. Triage means maintainer-facing item cards: URL, what each issue/PR is about, why it matters, author trust, fit, risk, proof/test state, blockers, and next action. Never return only queue numbers or opaque refs. Output is URL-first: every surfaced issue/PR/repo item must include its GitHub URL in the first line or first sentence for that item. If giving a shortlist, print one URL per item. Use RepoBar as the first pass only for broad queue discovery across relevant owners/orgs. RepoBar is faster and more profile-aware than hand-rolling gh repo list loops, and it already understands repo activity, issue counts, PR counts, local projects, auth, cache, and filters. Setup Prefer a real repobar binary when installed. In this workspace it may only exist as a SwiftPM product in ~/Projects/RepoBar. Default owners for broad triage: steipete, openclaw. For broad/default queue triage, include a detail pass for openclaw/openclaw even if it is not the first repo by count, because it is the main ClawdBot/OpenClaw queue. Do not include amantus-ai or other owners unless the user names them, the current repo is already under that owner, or the task explicitly asks for all/everything. For an exact owner-specific task, do not broaden beyond the named owner. Local Repo Gate Before starting work inside any local project, verify the checkout is ready: Proceed only when the branch is main, the pull succeeds, and the worktree is clean. If the branch is not main, the pull fails, or git status --short shows changes, stop and ask Peter what to do. Do not switch branches, stash, commit, reset, restore, or clean without explicit direction. Scope Rule If the user says triage and the current working directory is a Git repo with a GitHub remote, triage only that project. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills steipete/github-project-triage