github-triage

Solid

Triage, review, and label GitHub pull requests and issues from the terminal with gh-dash, octo.nvim, and gh. Use when reviewing agent-authored PRs, grooming an issue backlog, or deciding which labels to set.

Code & Development 4 stars 1 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
23
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Triage and Review GitHub Work Agents open most of the pull requests and issues here, so throughput is limited by review, not by authoring. The whole loop stays in the terminal. ## Tools | Tool | Role | | ----------- | ----------------------------------------------------------------------------------- | | `gh-dash` | Triage queue — cross-repository sections, approve/merge/comment/label inline (`gd`) | | `octo.nvim` | Review surface — line comments, review threads, submit/approve inside Neovim | | `gh` | Scripting and bulk operations | | `jq` | Structured queue filtering used by the bundled shell helper | | `delta` | Diff rendering, already wired as the `gh` pager | Configuration lives in `~/.config/gh-dash/config.yml`. Sections are scoped by identity (`involves:@me`, `review-requested:@me`) rather than by owner, so new repositories and orgs appear without editing the file. ## Triage Loop 1. Run `gd` (`gh-dash`). Work the PR sections left to right — they are ordered by how much they need a human: `Needs review` → `CI red` → `Changes requested` → `Ready to merge` → `Requested from me` → `Drafts`. 1. `CI red` first: a failing agent PR is bounced back with a comment (`c`), never reviewed line by line. 1. On a candidate, press `E` to open it in octo, ...

Details

Author
fmind
Repository
fmind/dotfiles
Created
4 months ago
Last Updated
yesterday
Language
Go
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category