Stats
Actions
Tags
From dmv
Tool selection hierarchy for GitHub interactions (gh CLI vs MCP server), setup, and pushing. Use when interacting with GitHub, setting up GitHub tools, or pushing to remote.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dmv:githubThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Prefer gh CLI over GitHub MCP server for all GitHub interactions.
Prefer gh CLI over GitHub MCP server for all GitHub interactions.
Task requires GitHub interaction
├─ Is gh installed? (`which gh`)
│ ├─ Yes → Does gh support this operation?
│ │ ├─ Yes → USE gh CLI
│ │ └─ No → USE GitHub MCP Server
│ └─ No → USE GitHub MCP Server
Prefer gh CLI for: PRs, issues, releases, CI status, PR comments/reviews, any well-supported workflow.
Use MCP Server for: when gh isn't installed, complex cross-repo searches, bulk data retrieval, operations gh doesn't support.
Use git pub instead of git push — it's a user alias that sets upstream tracking automatically.
If gh or the MCP server aren't configured:
brew install gh, then user must run gh auth login manually (interactive)/mcp and authenticates in the browsernpx claudepluginhub racurry/neat-little-package --plugin dmvGuides GitHub CLI (gh) commands for creating/managing PRs, issues, CI runs, releases, auth, and JSON scripting from terminal.
Provides GitHub CLI (gh) usage for repos, issues, PRs, releases, gists, and workflow dispatches. Includes safety gates for destructive operations and JSON projection recipes to reduce token usage.
Provides copy-paste ready GitHub CLI (gh) installation, authentication, and command usage. Prevents common mistakes like missing full paths or GITHUB_TOKEN prefix errors.