Structural code search that understands syntax. Find patterns like function calls, imports, class definitions - not just text.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionast-grep-findExecute the skills CLI command in your project's root directory to begin installation:
Fetches ast-grep-find from parcadei/continuous-claude-v3 and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate ast-grep-find. Access via /ast-grep-find in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
3.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
3.7K
stars
Structural code search that understands syntax. Find patterns like function calls, imports, class definitions - not just text.
uv run python -m runtime.harness scripts/ast_grep_find.py \
--pattern "import asyncio" --language python
uv run python -m runtime.harness scripts/ast_grep_find.py \
--pattern "async def \$FUNC(\$\$\$)" --language python --path "./src"
uv run python -m runtime.harness scripts/ast_grep_find.py \
--pattern "console.log(\$MSG)" --replace "logger.info(\$MSG)" \
--language javascript
uv run python -m runtime.harness scripts/ast_grep_find.py \
--pattern "print(\$X)" --replace "logger.info(\$X)" \
--language python --dry-run
| Parameter | Description |
|---|---|
--pattern |
AST pattern to search (required) |
--language |
Language: python, javascript, typescript, go, etc. |
--path |
Directory to search (default: .) |
--glob |
File glob pattern (e.g., **/*.py) |
--replace |
Replacement pattern for refactoring |
--dry-run |
Preview changes without applying |
--context |
Lines of context (default: 2) |
| Syntax | Meaning |
|---|---|
$NAME |
Match single node (variable, expression) |
$$$ |
Match multiple nodes (arguments, statements) |
$_ |
Match any single node (wildcard) |
# Find all function definitions
uv run python -m runtime.harness scripts/ast_grep_find.py \
--pattern "def \$FUNC(\$\$\$):" --language python
# Find console.log calls
uv run python -m runtime.harness scripts/ast_grep_find.py \
--pattern "console.log(\$\$\$)" --language javascript
# Replace print with logging
uv run python -m runtime.harness scripts/ast_grep_find.py \
--pattern "print(\$X)" --replace "logging.info(\$X)" \
--language python --dry-run
| Tool | Best For |
|---|---|
| ast-grep | Structural patterns (understands code syntax) |
| warpgrep | Fast text/regex search (20x faster grep) |
Use ast-grep when you need syntax-aware matching. Use warpgrep for raw speed.
Requires ast-grep server in mcp_config.json.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
parcadei/continuous-claude-v3
mattpocock/skills
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
ast-grep-find reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: ast-grep-find is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: ast-grep-find is focused, and the summary matches what you get after install.
I recommend ast-grep-find for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
I recommend ast-grep-find for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in ast-grep-find — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for ast-grep-find matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: ast-grep-find is the kind of skill you can hand to a new teammate without a long onboarding doc.
ast-grep-find is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for ast-grep-find matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 63