Standardize gh CLI usage for predictable JSON outputs across repositories.
npx skills add https://github.com/n4vysh/dotfiles --skill gh-n4vysh
Please help me install this Agent Skill. Skill: gh Source: https://github.com/n4vysh/dotfiles/tree/main/home/dot_agents/skills/gh Command: npx skills add https://github.com/n4vysh/dotfiles --skill gh-n4vysh
Streamline and standardize GitHub CLI (gh) usage within agents to produce predictable, parseable outputs.
Instruct the agent to list open PRs in OWNER/REPO with JSON output and limit to 100 results.
High-intent search queries and answers about installing and using this skill.
To get structured JSON output from gh CLI commands, you standardize agent usage by applying the --json flag. This enforces parseable results for reliable downstream processing and automation runs.
Listing issues across multiple GitHub repos is handled by standardizing repository targeting with the --repo flag and managing multi-page results using pagination limits to ensure predictable outputs.
To retrieve GitHub PR fields not exposed by standard gh commands, you fall back to gh api. This gracefully handles missing data fields and supports mixed workflows across repositories.
Yes, this approach supports categorizing open PRs in CI pipelines by automating issue and PR discovery. It generates summaries across multiple repos using structured outputs and pagination.
Standardizing gh CLI usage for agent runs ensures predictable, parseable outputs. Raw commands lack consistent formatting, whereas enforcing structured JSON and pagination handles multi-repo workflows reliably.
georgekhananaevWrap GitHub CLI commands with risk classification and confirmation prompts.
getsentryParse Sentry comments in GitHub PRs and generate targeted fixes.
ahmadawaisTransform unstructured updates into hierarchically formatted Slack-ready summaries with status tags.
superfhpSearch and retrieve academic papers from the arXiv repository via its REST API.
