github-project-triage

---
name: github-project-triage
description: "Use when working with gitHub issue/PR triage: summarize, assess risk/testability, inspect CI/diffs/trust from steipete/agent-scripts."
source: https://github.com/steipete/agent-scripts/tree/main/skills/github-project-triage
generated: 2026-05-27T20:55:47.872Z
category: tool
audience: engineers
---

## When to use

- Use this only when the scope is broad. Start with repo-level queue maps. This finds repos with open issues and/or PRs and gives counts.
- Using the github-project-triage skill's upstream workflow, guardrails, and local-tool assumptions.
- Auditing commands or operational steps before changing github project triage behavior.
- Needing a compact agent reference for gitHub issue/PR triage: summarize, assess risk/testability, inspect CI/diffs/trust.

## Key concepts

### 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. Do not broaden to all Peter/org queues unless the user says broad, all, everything, names multiple owners/orgs, or asks for cross-repo triage. If the repo has VISION.md, read it before judging what can be handled autonomously. Use it as the product-fit source of truth, then apply this skill's risk/testability rules. If no VISION.md exists, use the autonomous-fit rules...

### Autonomous Work Mode

When the user says do work autonomously, work you can do autonomously, keep going, or similar, do not stop after a queue summary or one local patch. Treat it as permission to process the eligible issue/PR queue sequentially until no safe autonomous item remains, each item is landed/closed/deferred with proof, or a blocker requires Peter. Never work multiple tickets at once. For each item: 1. Read the issue/PR, related code, docs, CI, and VISION.md if present; Google/use official docs when...

### Trust Signals

Include author/opener trust for every non-maintainer item you recommend acting on. For low-risk Dependabot/internal items, a terse bot/internal trust line is enough. Prefer the bundled helper: Fallback if this skill checkout lacks the helper: Also use github-author-context when a PR needs deeper trust judgment, especially for OpenClaw, security-sensitive changes, broad PRs, new accounts, or unusual author behavior. Prefer existing contributor notes first: Trust output must stay factual: Do...

### Item Evaluation

Classify each item: bug: require repro/log/failing test/current-main proof when feasible; identify root cause before recommending fix/merge. feature: require end-to-end test plan. If live validation needs a provider key, account, device, service, model access, or paid API, say exactly what credential/access is missing before work can be considered complete. dependency: explain package group, major/minor risk, failing checks, runtime/engine changes, and whether to split. security: raise...

### Fast Queue Map

Use this only when the scope is broad. Start with repo-level queue maps. This finds repos with open issues and/or PRs and gives counts. PR queue, primary triage order: Issue pressure, second pass when issues matter: Use --forks and --archived only when the user says "all", "everything", or asks for archaeology. Default triage should omit forks and archived repos unless their queues are specifically relevant. For a compact terminal view: Useful jq summary: When summarizing a PR-sorted queue...

## API reference

```
npx skills add steipete/agent-scripts --skill github-project-triage
```

Install the github-project-triage skill from steipete/agent-scripts.

```
npx skills add steipete/agent-scripts --skill github-project-triage
```

```
repobarcmd() {.
```

Command or snippet documented by the upstream github-project-triage skill.

```
repobar_cmd() {
  if command -v repobar >/dev/null 2>&1; then
    repobar "$@"
  elif [ -x "$HOME/Projects/RepoBar/.build/debug/repobarcli" ]; then
    "$HOME/Projects/RepoBar/.build/debug/repobarcli" "$@"
  else
    swift run --package-path "$HOME/Projects/RepoBar" repobarcli "$@"
  fi
}

repobar_cmd status --json
```

```
git status --short --branch.
```

Command or snippet documented by the upstream github-project-triage skill.

```
git status --short --branch
git branch --show-current
git pull --ff-only
git status --short --branch
```

```
repo=$(gh repo view --json nameWithOwner --jq.nameWithOwner 2>/dev/null || true).
```

Command or snippet documented by the upstream github-project-triage skill.

```
repo=$(gh repo view --json nameWithOwner --jq .nameWithOwner 2>/dev/null || true)
if [ -z "$repo" ]; then
  url=$(git remote get-url origin 2>/dev/null || true)
  repo=$(printf '%s\n' "$url" |
    sed -E 's#^git@github.com:##; s#^https://github.com/##; s#\\.git$##')
fi
printf '%s\n' "$repo"
```

```
gh issue list --repo "$repo" --state open --limit 50 \.
```

Command or snippet documented by the upstream github-project-triage skill.

```
gh issue list --repo "$repo" --state open --limit 50 \
  --json number,title,author,labels,createdAt,updatedAt,url
gh pr list --repo "$repo" --state open --limit 50 \
  --json number,title,author,isDraft,reviewDecision,mergeStateStatus,createdAt,updatedAt,url
```

```
gh issue view <n> --repo "$repo" \.
```

Command or snippet documented by the upstream github-project-triage skill.

```
gh issue view <n> --repo "$repo" \
  --json number,title,author,body,comments,labels,createdAt,updatedAt,url
gh pr view <n> --repo "$repo" \
  --json number,title,author,body,comments,files,commits,isDraft,reviewDecision,mergeStateStatus,statusCheckRollup,createdAt,updatedAt,url
gh pr diff <n> --repo "$repo" --patch
```

```
skills/github-project-triage/scripts/github-activity.sh --repo <owner/repo> --global <login>.
```

Command or snippet documented by the upstream github-project-triage skill.

```
skills/github-project-triage/scripts/github-activity.sh --repo <owner/repo> --global <login>
```

## Gotchas

- Prefer a real repobar binary when installed. In this workspace it may only exist as a SwiftPM product in ~/Projects/RepoBar.
- Never work multiple tickets at once. For each item:.
- Ask first: new features, product/vision choices, broad behavior changes, risky dependencies, security-sensitive changes without strong proof, live-provider work without usable credentials, anything that cannot be end-to-end tested.
- Do not end autonomous mode with dirty files or an unpushed local fix unless blocked. If blocked, state the exact blocker, current branch/status, proof already gathered, and the next decision needed.
- Prefer the bundled helper:.
- Do not treat trust as proof. It changes review depth, not correctness.
- prefer external/user-reported bugs and PRs with clear proof.
- Do not run destructive local actions (local reset, branch deletes, checkout moves) unless the user explicitly asks.

---
Generated by SkillMake from https://github.com/steipete/agent-scripts/tree/main/skills/github-project-triage on 2026-05-27T20:55:47.872Z.
Verify against source before relying on details.

File: ~/.claude/skills/github-project-triage/SKILL.md