gh-search
Skill8 starsChanged 45 days agoMITView on GitHub
Search GitHub from the terminal with `gh search` (repos, code, issues, prs) to find real-world code examples. Use when the user wants to see how an established project implements something, find a maintained example to borrow from, or check a repo's stars/contributors/activity before trusting its code — and when another skill needs vetted examples.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- aaddrick/gh-cli-searchtheir own version, first seen Oct 17, 2026
- Cogni-AI-OU/cogni-ai-agent-skillstheir own version, first seen May 19, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- aaddrick/gh-cli-search★ 9same name
- Cogni-AI-OU/cogni-ai-agent-skills★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository75 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- workspace/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ask-mattSkill
- codebase-designSkill
- code-reviewSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- improve-codebase-architectureSkill
- prototypeSkill
- pstack-architectSkill
- pstack-arenaSkill
- pstack-automate-meSkill
- pstack-blast-radiusSkill
- pstack-broSkill
- pstack-create-verification-skillSkill
- pstack-figure-it-outSkill
- pstack-howSkill
- pstack-interrogateSkill
- pstack-maintain-verification-skillSkill
- pstack-make-bot-uiSkill
- pstack-no-commentsSkill
- pstack-poteto-modeSkill
- pstack-principle-attack-the-premiseSkill
- pstack-principle-boundary-disciplineSkill
- pstack-principle-build-the-leverSkill
- pstack-principle-encode-lessons-in-structureSkill
- pstack-principle-exhaust-the-design-spaceSkill
- pstack-principle-experience-firstSkill
- pstack-principle-fix-root-causesSkill
- pstack-principle-foundational-thinkingSkill
- pstack-principle-guard-the-context-windowSkill
- pstack-principle-laziness-protocolSkill
- pstack-principle-make-operations-idempotentSkill
- pstack-principle-migrate-callers-then-delete-legacy-apisSkill
- pstack-principle-minimize-reader-loadSkill
- pstack-principle-model-the-domainSkill
- pstack-principle-never-block-on-the-humanSkill
- pstack-principle-outcome-oriented-executionSkill
- pstack-principle-prove-it-worksSkill
- pstack-principle-redesign-from-first-principlesSkill
- pstack-principle-separate-before-serializing-shared-stateSkill
- pstack-principle-sequence-verifiable-unitsSkill
- pstack-principle-subtract-before-you-addSkill
- pstack-principle-test-behavior-not-implementationSkill
- pstack-principle-type-system-disciplineSkill
- pstack-recallSkill
- pstack-reflectSkill
- pstack-setup-pstackSkill
- pstack-show-me-your-workSkill
- pstackSkill
- pstack-swarmSkill
- pstack-tddSkill
- pstack-teachSkill
- The first 60 shown.
The file
Files
gh-search
gh search finds code and repositories across GitHub from the terminal. Pick the subcommand that
matches the question; add --json + --jq to keep output small.
Searching
# Repos, by adoption
gh search repos <keywords> stars:>500 language:go archived:false --sort=stars \
--json fullName,stargazersCount,pushedAt,description --jq '.[]|"\(.stargazersCount)\t\(.fullName)"'
# The implementing file (not the README)
gh search code "sqlite3_update_hook language:go" --json repository,path,url
# How an error was fixed / an API was designed
gh search issues "<error text>" --state=closed
gh search prs "<feature>" --state=mergedQualifiers go in the query string: stars:>N, pushed:>YYYY-MM-DD, language:X, topic:X,
org:X, archived:false, in:name,description,readme. Code search reads the default branch only
and needs auth.
Stats gh search omits
gh search returns stars and forks. Before copying code, pull the numbers it leaves out — they
separate a maintained project from an abandoned one:
gh api repos/OWNER/REPO --jq '{stars:.stargazers_count, forks:.forks_count, pushed:.pushed_at, archived:.archived}'
gh api "search/issues?q=repo:OWNER/REPO+type:pr" --jq .total_count # PRs (openIssuesCount mixes both)
gh api "search/issues?q=repo:OWNER/REPO+type:issue" --jq .total_count # issues
gh api "repos/OWNER/REPO/contributors?per_page=1&anon=1" -i | grep -i '^link:' # last page number = contributor countRules
- Show a repo's stats before treating its code as a dependable example.
- Popular ≠ correct — read the code you copy.
- Cite the repo and file you copy from.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

