Trigger Phrases
Say any of these to activate this skill:
"check github""repo status""ci status""pr review""open prs""pull requests""github issues"
Tools Used
How It Works
When triggered, check GitHub repos and build a triage dashboard. Use the
pre-installed gh CLI via exec — do not connect GitHub or call GITHUB_* tools.
- Auth —
exec({ command: "gh auth status" }). If not authenticated, ask for a PAT, save it to.envasGITHUB_TOKEN, retry. - Fetch —
exec({ command: "gh pr list --state open" })exec({ command: "gh issue list --state open" })exec({ command: "gh run list --limit 20" })for CI
- Build canvas — Create or update a GitHub ops dashboard:
- KPIs: open PRs count, open issues count, CI passing/failing
- Table: PR review queue (repo, title, author, age, CI status, reviewers)
- Table: recent issues sorted by priority labels
- Alert — For PRs open >2 days with no reviewer:
send_messageto alert channel if configured
- Persist — Log findings to memory for trend tracking
If no repo is in the current git remote, ask the user which owner/repo to watch and pass -R owner/repo to gh.