You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A curated collection of search queries to discover AI coding assistant configurations in public repositories.
Why This Matters
GitHub's code search reveals real-world AI tool configurations that traditional searches miss. While official documentation shows you the format, queries like path:.claude/skills uncover how experienced developers actually configure their tools—patterns and techniques refined in production codebases.
The real power comes from combining path queries with keywords. Add any keyword before the path query to find configurations for specific domains, frameworks, or use cases:
You can use any keyword: framework names (Next.js, Laravel, Rails), languages (Rust, Go, Python), platforms (AWS, Vercel), or domains (e-commerce, auth, API).
Searching by Filename Pattern
The keyword search above looks inside file contents. To search only by filename, use wildcards in the path.
** matches any number of directories (recursive search)
* matches any characters within a filename (but not /)
? matches exactly one character (e.g., path:*.a?c matches file.abc, file.aac)
Path anchoring:
path:src/*.js matches src/app.js and app/src/main.js (unanchored)
path:/src/*.js matches only src/app.js at repository root (anchored with leading /)
Literal matching:
path:"file?" searches for literal file? (glob patterns disabled in quotes)
Nested directory patterns:
The trailing pattern matters for nested searches:
Pattern
Behavior
path:.claude
Substring match - any path containing ".claude"
path:.claude/
Paths within .claude directory
path:.claude/skills
All files in directory AND subdirectories
path:.claude/skills/**/*
Only files in subdirectories (direct children excluded)
Key insight:path:dir is more comprehensive than path:dir/**/* because the latter only matches files in subdirectories, missing direct children of the directory.
Recommended approach: Use the simpler pattern for comprehensive results:
path:.claude/skills
Use **/* only when you specifically want subdirectory files:
path:.claude/skills/**/*
Build your own query:
path:**/[directory]/**/*[keyword]*
Replace [directory] with the config folder (.claude, .cursor, .roo, etc.) and [keyword] with what you're looking for.
Start broad, then narrow down. Here's how to explore Claude Code configurations:
Step 1: Start with the tool's directory
path:.claude
> See all Claude Code configs (settings, rules, skills, hooks...)
Step 2: Narrow to a specific config type
path:.claude/skills
> Only skill files
Step 3: Add a keyword to find specific skills
api path:.claude/skills
> Skills related to API development
Step 4: Use OR for related terms
(api OR rest OR graphql) path:.claude/skills
> Catches different API styles
Another example: Exploring Cursor configurations
Step 1: path:.cursor > All Cursor configs
Step 2: path:.cursor/rules > Only rules
Step 3: typescript path:.cursor/rules > TypeScript-related rules
Step 4: (typescript OR javascript) path:.cursor/rules > Both TS and JS
Filter cheatsheet:
Filter
Purpose
Example
path:
Search in path
path:.claude/skills
path:**/
Any directory
path:**/CLAUDE.md
language:
Filter by language
language:python
symbol:
Function/class definitions
symbol:MyClass
content:
Only file contents
content:api
is:
Repository properties
NOT is:fork
OR
Match alternatives
(react OR vue)
NOT
Exclude
NOT path:node_modules
Note: Filters like stars:, pushed:, and fork: only work in repository search, not code search.
Known Limitations
Search Scope
Only the default branch is indexed (not other branches or tags)
Private repositories are not visible unless you have access
Deleted or old configs in commit history cannot be searched
You must be logged in to search code in public repositories
Query Limits
Query length: max 1000 characters
Boolean operators: max 5 AND, OR, or NOT per query
Results: 20 per page, max 5 pages (100 results viewable even if thousands match)
Code search doesn't support stars:, pushed:, fork: filters (these only work in repository search)
Tip: If your search returns too many results, narrow it down with additional keywords, path filters, or regex patterns to find what you need within the 100-result limit.
File Indexing Limits
Files over 350 KB are excluded
Empty files are not indexed
Binary files (PDF, images, etc.) are excluded
Only UTF-8 encoded files are indexed
Lines over 1024 characters are truncated
Other Notes
The filename: qualifier is deprecated; use path:**/filename instead
Identical files across repos may be collapsed (click "Show identical files" to expand)
Very large repositories may not be fully indexed
Regex look-around assertions ((?=...), (?!...)) are not supported
Contributing
Contributions are welcome! See CONTRIBUTING.md for guidelines.