Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From ds
GitHub CLI operations for issues, PRs, reviews, CI, and Copilot workflows. Use when working with pull requests, issues, CI status, code review, GitHub Copilot, triage, or PR shipping.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ds:githubThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<objective>
<quick_start>
For simple queries, use gh directly. See cli-patterns.md.
gh pr list # List open PRs
gh issue list # List open issues
gh pr view 42 # View PR #42
gh pr checks 42 # Check CI status
</quick_start>
Bundled scripts for data gathering (output JSON, run without loading into context).Script paths are relative to this SKILL.md file (not the working directory). Derive the absolute script path from this file's location:
/path/to/github/SKILL.md/path/to/github/scripts/Available scripts:
scripts/triage_gather.sh - Parallel PR/issue collectionscripts/pr_details.sh <number> - PR info + diff + checksscripts/copilot_activity.sh - Copilot activity summary
<reference_guides>
Require confirmation: merge, approve, close
- Use `--json` + `--jq` for scripting (more stable than text) - Include `--limit` for large result sets - For CI status, check `gh run list --branch` for latest (PR status can be stale) - Copilot author format varies by repo (check with `gh pr list --state all --json author`)<success_criteria> GitHub operations are successful when:
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.
npx claudepluginhub durandom/skills --plugin ds