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
Provides correct `gh search` syntax for GitHub CLI queries, handling exclusions, quotes, and platform differences. Use when searching for issues, PRs, repos, code, or commits to prevent shell parsing failures.
/plugin marketplace add aaddrick/gh-cli-search/plugin install gh-cli-search@helpful-tools-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Search GitHub from the command line using gh search subcommands. The key principle: Always use -- before queries with exclusions to prevent shell interpretation of - prefixes.
Use this skill when:
gh CLI for issues, PRs, repos, code, or commits| Subcommand | Use For | Common Flags |
|---|---|---|
gh search issues | Issues (add --include-prs for PRs too) | --label, --state, --author, --assignee |
gh search prs | Pull requests only | --label, --state, --author, --draft, --merged |
gh search repos | Repositories | --language, --stars, --topic, --owner |
gh search code | Code within files | --repo, --language, --filename |
gh search commits | Commit messages | --repo, --author, --committer |
-- FlagUnix/Linux/Mac:
gh search issues -- "bug -label:duplicate"
PowerShell:
gh --% search issues -- "bug -label:duplicate"
Why: The - prefix gets interpreted as a command flag without --. PowerShell needs --% to stop parsing.
Multi-word queries need quotes:
gh search issues "memory leak"
Entire query with spaces should be quoted:
gh search issues "bug label:urgent created:>2024-01-01"
Qualifier values with spaces need inner quotes:
gh search prs -- 'security label:"bug fix"'
Inline qualifiers (use within search query):
gh search repos "react stars:>1000 language:typescript"
Flag-based (use as separate flags):
gh search repos "react" --language typescript --stars ">1000"
Can mix both:
gh search issues "crash" --label bug created:>2024-01-01
>, >=, <, <= - Numeric: stars:>100, comments:>=5.. - Ranges: stars:10..50, created:2024-01-01..2024-12-31@me - Current user: author:@me, assignee:@me, owner:@mecreated:>2024-01-01 or created:2024-01-01..2024-12-31in:title - Search in title onlyin:body - Search in body onlyin:comments - Search in comments only-qualifier:value - Exclude: -label:bug, -language:javascriptNOT keyword - For words only: "hello NOT world"Find your open issues without bug label:
gh search issues -- "is:open author:@me -label:bug"
Find popular Python ML repos updated recently:
gh search repos "machine learning" --language python --stars ">1000" --updated ">2024-01-01"
Find PRs with specific label and text:
gh search prs -- 'security label:"bug fix" created:>2024-01-01'
Search code in organization repos:
gh search code "TODO" --owner myorg --language javascript
| Mistake | Problem | Fix |
|---|---|---|
gh search issues -label:bug | -label interpreted as flag | Add --: gh search issues -- "-label:bug" |
gh search repos machine learning | Searches "machine" OR "learning" | Quote it: "machine learning" |
in:title outside quotes | Shell interprets : oddly | Include in query: "crash in:title" |
Mixing @ with value | Invalid syntax | Use @me or username, not both: author:@me ✓, author:@username ✗ (drop @) |
PowerShell without --% | Parsing breaks with exclusions | Add gh --% before command |
All subcommands support:
--limit <n> - Max results (default: 30, max: 1000)--json <fields> - JSON output for scripting--web - Open results in browser--sort <field> - Sort by: comments, created, reactions, updated, stars, etc.--order asc|desc - Sort direction (default: desc)Correct syntax prevents:
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.