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 / 3 months ago

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

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

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

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

If you like that workflow you might love CheepCode[0] which I built specifically to support it! CheepCode connects to Linear and works on tickets as they roll in, submitting PRs to GitHub. [0] https://cheepcode.com. - Source: Hacker News / about 1 year ago