Skip to main content
toolsSource-backed
ast-grep logo

ast-grep

Open-source CLI for structural code search, linting, and rewriting with abstract syntax tree patterns.

by ast-grep · submitted by oktofeesh1·added 2026-06-03·
HarnessCLI
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://ast-grep.github.io/guide/introduction.html, https://github.com/ast-grep/ast-grep, https://ast-grep.github.io/
Brand
ast-grep
Brand domain
ast-grep.github.io
Brand asset source
brandfetch
Safety notes
ast-grep can rewrite many files quickly, so run searches, tests, and version-control review before applying broad fixes., Structural patterns can still overmatch when rules are too broad; use narrow language settings, test cases, and staged changes for codemods., Custom YAML rules and scripts should be reviewed before use in CI or automated agent workflows.
Privacy notes
ast-grep primarily runs locally over source files and does not require uploading code to a hosted service for normal CLI use., Search results, JSON output, logs, CI artifacts, and generated patches may expose source snippets or proprietary code., Any package manager, editor extension, CI integration, or third-party wrapper around ast-grep may have its own telemetry or network behavior.
Author
ast-grep
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-03

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

78

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Copy & paste

Copy-ready — paste the snippet to get started.

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup. Includes a review or approval gate.

0/3 ready
Review & approval2General1

Safety & privacy surface

Safety & privacy surface

3 safety and 3 privacy notes across 5 risk areas. Review closely: network access.

5 areas
  • SafetyLocal filesast-grep can rewrite many files quickly, so run searches, tests, and version-control review before applying broad fixes.
  • SafetyGeneralStructural patterns can still overmatch when rules are too broad; use narrow language settings, test cases, and staged changes for codemods.
  • SafetyExecution & processesCustom YAML rules and scripts should be reviewed before use in CI or automated agent workflows.
  • PrivacyNetwork accessast-grep primarily runs locally over source files and does not require uploading code to a hosted service for normal CLI use.
  • PrivacyData retentionSearch results, JSON output, logs, CI artifacts, and generated patches may expose source snippets or proprietary code.
  • PrivacyNetwork accessAny package manager, editor extension, CI integration, or third-party wrapper around ast-grep may have its own telemetry or network behavior.

Disclosure: editorial

Safety notes

  • ast-grep can rewrite many files quickly, so run searches, tests, and version-control review before applying broad fixes.
  • Structural patterns can still overmatch when rules are too broad; use narrow language settings, test cases, and staged changes for codemods.
  • Custom YAML rules and scripts should be reviewed before use in CI or automated agent workflows.

Privacy notes

  • ast-grep primarily runs locally over source files and does not require uploading code to a hosted service for normal CLI use.
  • Search results, JSON output, logs, CI artifacts, and generated patches may expose source snippets or proprietary code.
  • Any package manager, editor extension, CI integration, or third-party wrapper around ast-grep may have its own telemetry or network behavior.

Prerequisites

  • Local source checkout for the codebase being searched, linted, or rewritten.
  • ast-grep CLI installed from a reviewed package source such as npm, pip, cargo, Homebrew, Scoop, mise, MacPorts, or a source build.
  • Language selection and rule patterns reviewed against representative files before large repository scans or rewrites.

Schema details

Install type
copy
Troubleshooting
No
Source repository stats
Scope
Source repo
Tool listing metadata
Pricing
open-source
Disclosure
editorial
Application category
DeveloperApplication
Operating system
macOS, Windows, Linux
Full copyable content
## Editorial notes

ast-grep is useful when Claude or an engineering agent needs structural code search instead of brittle text matching. It lets teams search and rewrite code using patterns that look like ordinary code, backed by tree-sitter parsing, so large refactors, lint rules, and migration checks can target syntax shape rather than raw strings.

## Source notes

- The official README describes ast-grep as a CLI tool for code structural search, linting, and rewriting.
- The documentation describes ast-grep as an AST-based tool that searches code by pattern code instead of plain text.
- The guide covers command-line one-liners, YAML rule configuration, linting rules, project scans, code rewriting, editor integration, and language support.
- The GitHub repository is `ast-grep/ast-grep`, is MIT licensed, and describes the project as written in Rust.

## Duplicate check

Checked current `content/tools/`, open pull requests, live HeyClaude search results, and repository-wide content for `ast-grep`, `ast grep`, `astgrep`, `ast-grep.github.io`, `github.com/ast-grep/ast-grep`, `structural search`, `semantic code search`, `repository map`, and `codemod`. Related ast-grep MCP and Claude skill projects exist upstream, but no dedicated ast-grep tools entry, source URL duplicate, or open duplicate PR was found.

## Disclosure

Editorial listing. No paid placement or affiliate link is used.

About this resource

Editorial notes

ast-grep is useful when Claude or an engineering agent needs structural code search instead of brittle text matching. It lets teams search and rewrite code using patterns that look like ordinary code, backed by tree-sitter parsing, so large refactors, lint rules, and migration checks can target syntax shape rather than raw strings.

Source notes

  • The official README describes ast-grep as a CLI tool for code structural search, linting, and rewriting.
  • The documentation describes ast-grep as an AST-based tool that searches code by pattern code instead of plain text.
  • The guide covers command-line one-liners, YAML rule configuration, linting rules, project scans, code rewriting, editor integration, and language support.
  • The GitHub repository is ast-grep/ast-grep, is MIT licensed, and describes the project as written in Rust.

Duplicate check

Checked current content/tools/, open pull requests, live HeyClaude search results, and repository-wide content for ast-grep, ast grep, astgrep, ast-grep.github.io, github.com/ast-grep/ast-grep, structural search, semantic code search, repository map, and codemod. Related ast-grep MCP and Claude skill projects exist upstream, but no dedicated ast-grep tools entry, source URL duplicate, or open duplicate PR was found.

Disclosure

Editorial listing. No paid placement or affiliate link is used.

Source citations

Add this badge to your README

Show that ast-grep is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/tools/ast-grep.svg)](https://heyclau.de/entry/tools/ast-grep)

How it compares

ast-grep side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.

Field

Open-source CLI for structural code search, linting, and rewriting with abstract syntax tree patterns.

Open dossier

Open-source status companion for Claude Code and Codex with live local session state, your-turn alerts, usage views, and native macOS and Windows applications.

Open dossier

Open-source LLMOps platform for prompt management, prompt versioning, evaluation, and observability across LLM applications.

Open dossier

Open-source observability platform and SDK for tracing, debugging, replaying, and cost-monitoring AI agent and LLM application runs.

Open dossier
Next stepsDiffers
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffersoktofeesh1tristan666666oktofeesh1oktofeesh1
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brandast-grep logoast-grepAgent Island logoAgent IslandAgenta logoAgentaAgentOps logoAgentOps
Categorytoolstoolstoolstools
SourceSource-backedSource-backedSource-backedSource-backed
Authorast-grepTristan TangAgentaAgentOps
Added2026-06-032026-07-152026-06-032026-06-03
Platforms
Harness
Source repo
Safety notesast-grep can rewrite many files quickly, so run searches, tests, and version-control review before applying broad fixes. Structural patterns can still overmatch when rules are too broad; use narrow language settings, test cases, and staged changes for codemods. Custom YAML rules and scripts should be reviewed before use in CI or automated agent workflows.Agent Island reads local Claude Code and Codex session files to determine session state; review the requested filesystem access before use. The macOS release is ad-hoc signed rather than Apple-notarized, so first launch requires right-clicking the app and choosing Open. Windows packages are distributed through GitHub Releases, Scoop, and winget; verify the release source before installation.Agenta can manage and deploy prompt or configuration changes, so production updates should go through review and rollback controls. Webhooks and GitHub automations tied to prompt or deployment changes should be scoped to trusted repositories and guarded workflows. Evaluation and online monitoring results should support, not replace, domain review for high-risk application behavior.AgentOps instruments LLM calls, tools, operations, and agent workflows, so enable it intentionally in environments where captured traces are allowed. Cost and latency dashboards are useful for operations, but alerting and budget decisions still need human-reviewed thresholds. Self-hosted deployments require normal backend hardening for database access, secrets, authentication, and retained trace data.
Privacy notesast-grep primarily runs locally over source files and does not require uploading code to a hosted service for normal CLI use. Search results, JSON output, logs, CI artifacts, and generated patches may expose source snippets or proprietary code. Any package manager, editor extension, CI integration, or third-party wrapper around ast-grep may have its own telemetry or network behavior.Session monitoring is local and the project states that the app has no Agent Island account and no product telemetry. Usage views may call provider usage APIs with existing local credentials; those requests remain subject to the provider's privacy terms. Local transcript files and provider credentials can contain sensitive data and should not be included in public screenshots, issues, or logs.Prompt records, variants, test sets, traces, model inputs and outputs, feedback, annotations, and evaluation results may be stored in Agenta. Hosted Agenta use sends that data to Agenta Cloud; self-hosted deployments still require retention, access-control, and backup policies. Review Agenta's sensitive-data redaction and retention guidance before sending production, customer, or regulated data.Traces can include prompts, completions, tool inputs, tool outputs, errors, costs, tokens, tags, and application metadata. The docs say AgentOps automatically collects basic host environment details such as OS, Python version, anonymized hostname, and SDK version. Hosted dashboard use sends telemetry to AgentOps infrastructure; self-hosted use still requires retention, access-control, and log-review policies.
Prerequisites
  • Local source checkout for the codebase being searched, linted, or rewritten.
  • ast-grep CLI installed from a reviewed package source such as npm, pip, cargo, Homebrew, Scoop, mise, MacPorts, or a source build.
  • Language selection and rule patterns reviewed against representative files before large repository scans or rewrites.
  • macOS 13 or later, or Windows 10 or later.
  • A local Claude Code or Codex installation with session data available to the current user.
  • LLM application, prompt workflow, or agent workflow whose prompts and configurations need shared management.
  • Access to Agenta Cloud or a reviewed self-hosted Agenta deployment.
  • Provider credentials and a release policy for test sets, traces, prompt versions, and production deployment approvals.
  • Python or TypeScript/JavaScript application using a supported LLM provider or agent framework.
  • AgentOps project/API key for hosted dashboard use, or a reviewed self-hosted deployment plan.
  • A telemetry policy for which prompts, responses, tool calls, metadata, and host details may be captured.
Install
brew install tristan666666/tap/agentisland
Config
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.