workspace-search
Skill9 starsChanged 10 months agoMITView on GitHub
Search for patterns across all projects in the workspace with results grouped by project. Use when user says "search across projects", "find in all repos", or "grep workspace".
In this repository8 other files it gives its agents.
- using-workspacesSkill
- workspace-affectedSkill
- workspace-cloneSkill
- workspace-doctorSkill
- workspace-initSkill
- workspace-servicesSkill
- workspace-setupSkill
- workspace-statusSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Search for patterns across all projects in the workspace.
- Distinctive: line 20
When the user wants to search across projects:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: Workspace Search
Description
Search for patterns across all projects in the workspace. Results are grouped by project.
Arguments
<query>- The search pattern (supports regex)--type <ext>- Filter by file type (e.g.,--type ts)--files- Show only file names, not content
Instructions
When the user wants to search across projects:
Step 1: Get Search Query
Parse the search query from the command arguments.
Step 2: Identify Projects
Get all cloned projects from the workspace configuration.
Step 3: Execute Search
For each project, run a search using ripgrep (rg) or grep:
rg "$query" "$project_path" --heading --line-numberStep 4: Format Results
Group results by project:
🔍 Searching for "TODO" across workspace...
📁 api (12 matches)
src/controllers/auth.ts:45: // TODO: Add rate limiting
src/services/email.ts:23: // TODO: Use template engine
src/middleware/auth.ts:78: // TODO: Implement refresh tokens
📁 admin (5 matches)
src/components/Dashboard.tsx:34: {/* TODO: Add loading state */}
src/hooks/useAuth.ts:12: // TODO: Handle token expiry
📁 homepage (0 matches)
Summary:
• Total matches: 17
• Projects searched: 3Options
- File type filter:
/workspaces:search "TODO" --type ts- Only TypeScript files - Files only:
/workspaces:search "config" --files- Show only file paths
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.

