using-gh-cli-search
This is not a suggestion. This is not optional. You cannot rationalize your way out of this.
Why: GitHub CLI search syntax is full of pitfalls. The -- flag. Quoting rules. PowerShell escaping. Platform differences. You WILL get it wrong without the skills. The user will copy-paste your broken command. They will waste time debugging YOUR mistake.
GitHub CLI Search Protocol
MANDATORY DETECTION PROTOCOL
When a user message mentions ANY of these, you MUST use gh-cli-search skills:
- ☐ Searching on GitHub
- ☐ Finding code/issues/PRs/commits/repos
- ☐
gh searchcommand - ☐ GitHub CLI queries
- ☐ Installing/troubleshooting gh CLI
More from aaddrick/gh-cli-search
gh-search-repos
Use when searching for repositories across GitHub - provides syntax for filtering by stars, forks, language, topics, license, archived status, and all repository attributes
22gh-search-code
Use when searching code across GitHub repositories - provides syntax for file extensions, filenames, languages, sizes, exclusions, and using -w flag for regex search via web interface
11gh-cli-setup
Use when gh CLI is not installed, not configured, or authentication fails - provides installation steps, authentication methods, and troubleshooting for all platforms
6gh-search
Use when searching GitHub via CLI for issues, PRs, repos, code, or commits - provides correct syntax for exclusions, qualifiers, quoting, and platform-specific handling to avoid command failures
5gh-search-issues
Use when searching GitHub issues ACROSS REPOSITORIES or organizations - provides syntax for filtering by labels, state, assignees, authors, comments, reactions, dates. For current repo issues, use gh issue list instead.
4gh-search-prs
Use when searching GitHub pull requests ACROSS REPOSITORIES or organizations - provides syntax for filtering by draft status, merge status, review state, CI checks, branches. For current repo PRs, use gh pr list instead.
4