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

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

Every commit has a message. Every PR has a title and description. The status update already exists. It's just locked in GitHub. Who this is for: - Founders updating investors - PMs writing release notes - CEOs who want visibility without standups - Anyone who asks "what shipped?" and waits for an engineer to respond What it does: Connect your repos. Ask questions: - "What shipped this month?" - "Who... - Source: Hacker News / 7 months ago

Gitmore (https://gitmore.io) – natural language queries across GitHub, GitLab, and Bitbucket. Instead of filtering PRs, scanning commit logs, or asking engineers for updates: - "What shipped last week?" - "Who's been working on the API?" - "Which PRs have been open longest?" - "Summarize this month's releases" Plain English in, plain English out. How it works: Connect your repos via OAuth. We register... - Source: Hacker News / 7 months ago

If you're a founder who doesn't code, you probably rely on engineers to tell you what's shipping. That works until investors ask for updates, customers want a changelog, or you just need to know where things stand. What it does: Connect your repos. Ask questions: "What shipped last week?" "What's in progress?" "Who worked on what?" Get plain English answers from your commit history. Automated reports: Schedule... - Source: Hacker News / 7 months ago

Gitmore (https://gitmore.io) One feature I built that's been useful: a Slack bot that queries your Git history. Connect your repos. Add the bot to Slack. Ask:. - Source: Hacker News / 7 months ago

- 2FA support GitHub, GitLab, Bitbucket – one dashboard. Free for 1 repo: https://gitmore.io How do you currently handle investor questions about engineering progress? - Source: Hacker News / 7 months ago