smith-gh-cli

Outline safe and efficient GitHub CLI command practices for pagination, tokens, and permissions.

1|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/tianjianjiang/smith --skill smith-gh-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smith-gh-cli
Source: https://github.com/tianjianjiang/smith/tree/main/smith-gh-cli
Command: npx skills add https://github.com/tianjianjiang/smith --skill smith-gh-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub CLI users frequently encounter gotchas like inefficient pagination, mismanaged tokens, and risky commands. This skill provides best practices to optimize gh usage and prevent common mistakes.

Core Features & Use Cases

  • Token efficiency guidance: avoid unnecessary authentication steps and overly broad scopes.
  • Pagination & API usage: handle large result sets safely and efficiently.
  • Error prevention: recommended patterns to prevent accidental destructive actions.
  • Use Case: When reviewing many pull requests in a large repository, apply these rules to minimize API calls and stay within rate limits.

Quick Start

Run gh pr list with explicit flags to limit results and avoid token leakage.

Frequently Asked Questions about smith-gh-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle GitHub CLI pagination safely when reviewing many pull requests?

Handle GitHub CLI pagination safely by using explicit flags to limit results, which minimizes API calls and prevents rate limit exhaustion during large repository pull request reviews.

What is the best way to manage GitHub CLI tokens to avoid authentication errors?

GitHub CLI token management is optimized by avoiding unnecessary authentication steps and overly broad scopes, preventing token leakage and ensuring efficient command execution.

How does GitHub CLI command efficiency prevent accidental destructive actions?

GitHub CLI command efficiency prevents accidental destructive actions through recommended command patterns and robust permission checks, ensuring safe repository management and automation.

Can I use GitHub CLI for automation across large projects without hitting API limits?

You can use GitHub CLI for automation across large projects by applying safe efficiency practices, ensuring correct pagination handling and token efficiency to stay within API rate limits.

Why does my GitHub CLI script fail when processing large result sets?

GitHub CLI scripts fail processing large result sets due to inefficient pagination and mismanaged tokens, which this skill corrects by applying explicit flags and safe command patterns.