gh-grep
GitHub Grep
Base directory for this skill: /home/hazeruno/.config/opencode/skills/gh-grep
Search for real-world code examples across over a million public GitHub repositories via grep.app.
When to Use
- Finding implementation patterns for unfamiliar APIs or libraries
- Looking for correct syntax, parameters, or configuration examples
- Discovering production-ready code examples and best practices
- Understanding how different libraries/frameworks work together
Quick Start
Run the CLI script with bun (use absolute path):
bun /home/hazeruno/.config/opencode/skills/gh-grep/scripts/grep.ts searchGitHub --query "<code-pattern>" [options]
Core Options
| Option | Description |
|---|---|
--query |
Literal code pattern (required) |
--match-case |
Case-sensitive search |
--match-whole-words |
Match whole words only |
--use-regexp |
Interpret query as regex |
--repo |
Filter by repository (e.g., facebook/react) |
--path |
Filter by file path (e.g., src/components/) |
--language |
Filter by language (comma-separated, e.g., TypeScript,TSX) |
Global Options
-t, --timeout <ms>: Call timeout (default: 30000)-o, --output <format>: Output format:text|markdown|json|raw
Search Patterns
Important: This tool searches for literal code patterns, not keywords.
Good searches:
useState(- Find React useState usageimport React from- Find React import statementsasync function- Find async function declarations
Bad searches:
react tutorial- Keywords, not codebest practices- Concepts, not patternshow to use- Questions, not code
For detailed pattern examples and regex usage, see references/api_reference.md.
Common Examples
# Find Authentication Patterns
bun /home/hazeruno/.config/opencode/skills/gh-grep/scripts/grep.ts searchGitHub \
--query "getServerSession" --language "TypeScript,TSX"
# Find Error Boundary Implementations
bun /home/hazeruno/.config/opencode/skills/gh-grep/scripts/grep.ts searchGitHub \
--query "ErrorBoundary" --language "TSX"
# Find useEffect Cleanup with Regex
bun /home/hazeruno/.config/opencode/skills/gh-grep/scripts/grep.ts searchGitHub \
--query "(?s)useEffect\(\(\) => {.*removeEventListener" --use-regexp true
# Find CORS Handling in Flask
bun /home/hazeruno/.config/opencode/skills/gh-grep/scripts/grep.ts searchGitHub \
--query "CORS(" --match-case true --language "Python"
# Search Within Specific Repository
bun /home/hazeruno/.config/opencode/skills/gh-grep/scripts/grep.ts searchGitHub \
--query "createContext" --repo "facebook/react"
Requirements
- Bun runtime
mcporterpackage (embedded in script)
Resources
scripts/grep.ts- Main CLI tool wrapping grep.app MCP serverreferences/api_reference.md- Detailed parameter documentation and regex patterns
More from huynguyen03dev/opencode-setup
context7
Fetch up-to-date documentation and code examples for any library or framework. Use when needing API references, code examples, library documentation, or framework guides. Supports React, Next.js, MongoDB, Supabase, and thousands of other libraries.
15deep-wiki
Access AI-generated documentation and insights for GitHub repositories via DeepWiki. This skill should be used when exploring unfamiliar codebases, understanding repository architecture, finding implementation patterns, or asking questions about how a GitHub project works. Supports any public GitHub repository.
15github
Interact with GitHub repositories, issues, pull requests, and code via the GitHub MCP server. This skill should be used when managing repositories, creating/updating files, working with issues and PRs, searching code/repos/users, creating branches, and performing code reviews. Supports all major GitHub API operations.
11chrome-devtools
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.
11sequential-thinking
Dynamic problem-solving through structured sequential thoughts. Use when breaking down complex problems, planning multi-step solutions, analyzing ambiguous requirements, debugging intricate issues, exploring design alternatives, or tackling problems where the full scope is unclear. Enables thought revision, branching, and iterative refinement.
11code-review
Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.
10