Regex-based file search across repository contents using gh-grep extension. Use when searching code files for patterns, not issue content.
Regex-based file content search across GitHub repositories using gh-grep. Use when searching code files, docs, or configs for patterns—not issues or PRs.
/plugin marketplace add terrylica/claude-code-skills-github-issues/plugin install github-issues-operations@github-issues-skillsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Capability: Regex-based file content search across GitHub repositories using gh-grep
When to use: Searching repository files (code, docs, configs) - NOT issues
Installation Required: gh extension install k1LoW/gh-grep
┌─────────────────────────────────────────────────────┐
│ SEARCH DECISION │
├─────────────────────────────────────────────────────┤
│ │
│ gh search issues → Search ISSUES/PRs │
│ (searching-issues skill) │
│ │
│ gh grep → Search FILES (code, docs) │
│ (THIS skill) │
│ │
└─────────────────────────────────────────────────────┘
# Search in repository
gh grep "authentication" --owner myorg --repo myrepo
# Search with regex
gh grep "Bug.*critical" --owner myorg --repo myrepo
# Search specific file types
gh grep "API_KEY" --owner myorg --repo myrepo --include "*.env*"
# Case-insensitive search
gh grep -i "password" --owner myorg --repo myrepo
# Find function definitions
gh grep "function.*login" --owner myorg --repo myrepo
# Find TODO comments
gh grep "TODO:" --owner myorg --repo myrepo --include "*.js,*.ts"
# Find environment variables
gh grep "process\.env\." --owner myorg --repo myrepo
# Find imports
gh grep "^import.*axios" --owner myorg --repo myrepo
# Show line numbers
gh grep "error" --owner myorg --repo myrepo --line-number
# Show file names only
gh grep "config" --owner myorg --repo myrepo --files-with-matches
# Limit results
gh grep "api" --owner myorg --repo myrepo --max-count 10
# Include specific files
gh grep "test" --owner myorg --repo myrepo --include "*.test.js"
# Exclude files
gh grep "console" --owner myorg --repo myrepo --exclude "node_modules/*"
# Multiple file types
gh grep "interface" --owner myorg --repo myrepo --include "*.ts,*.tsx"
# Search specific branch
gh grep "feature" --owner myorg --repo myrepo --branch develop
# Search multiple repositories
for repo in repo1 repo2 repo3; do
gh grep "authentication" --owner myorg --repo $repo
done
# Exact word match
gh grep "\bpassword\b" --owner myorg --repo myrepo
# Start of line
gh grep "^export" --owner myorg --repo myrepo
# End of line
gh grep ";$" --owner myorg --repo myrepo --include "*.js"
# Optional characters
gh grep "colou?r" --owner myorg --repo myrepo
# Character classes
gh grep "[0-9]{3}-[0-9]{4}" --owner myorg --repo myrepo
# Function with any parameters
gh grep "function \w+\(.*\)" --owner myorg --repo myrepo
# Multiword match
gh grep "error.*handler" --owner myorg --repo myrepo
# Negation (find lines WITHOUT pattern)
gh grep "import" --owner myorg --repo myrepo | grep -v "node_modules"
# Find hardcoded secrets
gh grep "api_key.*=.*['\"]" --owner myorg --repo myrepo --include "*.js,*.ts,*.py"
# Find password patterns
gh grep -i "password\s*=\s*['\"][^'\"]+['\"]" --owner myorg --repo myrepo
# Find environment variable leaks
gh grep "AWS_SECRET" --owner myorg --repo myrepo
# Find TODO/FIXME comments
gh grep -i "TODO|FIXME" --owner myorg --repo myrepo
# Find console.log statements
gh grep "console\.log" --owner myorg --repo myrepo --include "*.js,*.ts"
# Find deprecated APIs
gh grep "deprecated" --owner myorg --repo myrepo --include "*.md"
# Find specific package usage
gh grep "import.*lodash" --owner myorg --repo myrepo
# Find external API calls
gh grep "axios\.|fetch\(" --owner myorg --repo myrepo
# Find database queries
gh grep "SELECT.*FROM" --owner myorg --repo myrepo
# Find markdown links
gh grep "\[.*\]\(.*\)" --owner myorg --repo myrepo --include "*.md"
# Find code examples in docs
gh grep "^```" --owner myorg --repo myrepo --include "*.md"
# Find heading references
gh grep "^#{1,3} " --owner myorg --repo myrepo --include "*.md"
#!/bin/bash
# Search across multiple repositories
PATTERN="authentication"
OWNER="myorg"
REPOS=("repo1" "repo2" "repo3")
for repo in "${REPOS[@]}"; do
echo "=== Searching $repo ==="
gh grep "$PATTERN" --owner "$OWNER" --repo "$repo" --line-number
echo ""
done
Speed:
Rate Limits:
Best Practices:
--include to reduce search scope--max-count for quick verification| Feature | gh grep | gh search issues |
|---|---|---|
| Searches | Repository files | Issues/PRs |
| Regex | ✅ Full regex support | ❌ No regex |
| Wildcards | ✅ Yes | ❌ No |
| Context | ✅ Line-based | ❌ No context |
| File types | ✅ Filter by extension | N/A |
| Installation | Extension required | Native |
| Use case | Code/docs search | Issue/PR search |
gh grep (this skill)gh search issues (searching-issues skill)gh models (ai-assisted-operations skill)Installation: gh extension install k1LoW/gh-grep
Maintenance Status: Actively maintained (211 stars, updated daily)
Full Extension Guide: GITHUB_CLI_EXTENSIONS.md
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.