ast-grep Reviews

GitHub Codespaces Reviews

ast-grep mentions (24)

• The Self-Driving Codebase: Full Agent Automation with Otter

  The previous post covered how we structured the codebase: Effect conventions, ast-grep enforcement, Drift, and CLAUDE.md to collaborate with Claude Code. You describe what you want, review the output, iterate. That works well. This post is about what happens when you step away entirely: giving the agent a list of issues and letting it work through them while you do something else. In autonomous mode, there's no... - Source: dev.to / 2 months ago

• How we use Effect and ast-grep to make our codebase work better with agents

  We use ast-grep as a structural syntax scanner that operates on the syntax tree of code (using tree-sitter under the hood). You define patterns in a YAML file, and it matches those patterns against the codebase. Critically, it’s run as part of the CI pipeline and configured to exit with an error when a banned pattern is found. And they have to be errors, not warnings. We learned this the hard way. Warnings get... - Source: dev.to / 3 months ago

• Less human AI agents, please

  I linked this elsewhere but, the agent could have a skill to use https://ast-grep.github.io/ to perform such mechanical code changes. - Source: Hacker News / 3 months ago

• Less human AI agents, please

  The proper tool for this is ast-grep (sg) https://ast-grep.github.io/ And an agent can learn to use sg with a skill too. (Or they can use sed) The issue is, at every point you do a replace, you need to verify if it was the right thing to do or if it was a false positive. If you are doing this manually, there's the time to craft the sed or sg query, then for each replacement you need to check it. If there are... - Source: Hacker News / 3 months ago

• Be intentional about how AI changes your codebase

  We use https://ast-grep.github.io (on a pre-commit hook). Bridges the linter gaps nicely. - Source: Hacker News / 4 months ago

GitHub Codespaces mentions (152)

• OpenCode Hit 140K Stars. Why Terminal Agents Won 2026.

  First, remote dev environments became table stakes. GitHub Codespaces, Gitpod, and self-hosted dev containers became how serious teams worked. Every engineer I know who ships to production now SSHs into a box they didn't provision, edits files with whatever editor is installed, and commits from a terminal. An IDE-bound agent requires you to also forward your IDE to the remote box, which most people don't bother... - Source: dev.to / 3 months ago

• Introducing codespaces.el: The Best Way to Use GitHub Codespaces

  This package provides support for managing GitHub Codespaces in Emacs and connecting to them via TRAMP. It provides a handy completing-read UI that lets you choose from all your created codespaces. - Source: dev.to / 5 months ago

• Don't get scammed on an interview.

  GitHub Codespaces provides 60 hours of free compute time every month, which is more than enough for scoped home assignments or interviews. It’s a full VSCode in the browser at github.dev or vscode.dev. - Source: dev.to / 8 months ago

• Stop Wasting Hours on Environment Setup - These Tools Will Save Your Sanity

  GitHub Codespaces - Cloud development. - Source: dev.to / about 1 year ago

• VSCode's SSH Agent Is Bananas

  https://github.com/features/codespaces All you need is a well-defined .devcontainer file. Debugging, extensions, collaborative coding, dependant services, OS libraries, as much RAM as you need (as opposed to what you have), specific NodeJS Versions — all with a single click. - Source: Hacker News / over 1 year ago