Full AI-Based Workflow
So I just built a system that on pre-push, watch changes to GH actions using CLI and feed errors to Claude. I am cloning the repo in 5 separate editors with a prompt that makes it develop, commit and push working code at all times. It leans heavily on static analysis and linting with Biome to ensure maximum correctness and strong guidelines for testing. Repository is a monorepo which has cohesive services that can be developed independently. Trunk-Based development and changes go straight to production (there's a post-deploy check that runs smoke tests) I'm not sure if anyone else has built something like this, but essentially I can "git clone" a new version of the repository in a different folder and literally multiply myself by just spending a couple minutes creating a prompt 99% of the Job is designing prompts and adjusting the pieces to be independent so I can fit in the recent part of the context window WHAT THE ACTUAL FUCK? 1 comments on Hacker News.
So I just built a system that on pre-push, watch changes to GH actions using CLI and feed errors to Claude. I am cloning the repo in 5 separate editors with a prompt that makes it develop, commit and push working code at all times. It leans heavily on static analysis and linting with Biome to ensure maximum correctness and strong guidelines for testing. Repository is a monorepo which has cohesive services that can be developed independently. Trunk-Based development and changes go straight to production (there's a post-deploy check that runs smoke tests) I'm not sure if anyone else has built something like this, but essentially I can "git clone" a new version of the repository in a different folder and literally multiply myself by just spending a couple minutes creating a prompt 99% of the Job is designing prompts and adjusting the pieces to be independent so I can fit in the recent part of the context window WHAT THE ACTUAL FUCK?
So I just built a system that on pre-push, watch changes to GH actions using CLI and feed errors to Claude. I am cloning the repo in 5 separate editors with a prompt that makes it develop, commit and push working code at all times. It leans heavily on static analysis and linting with Biome to ensure maximum correctness and strong guidelines for testing. Repository is a monorepo which has cohesive services that can be developed independently. Trunk-Based development and changes go straight to production (there's a post-deploy check that runs smoke tests) I'm not sure if anyone else has built something like this, but essentially I can "git clone" a new version of the repository in a different folder and literally multiply myself by just spending a couple minutes creating a prompt 99% of the Job is designing prompts and adjusting the pieces to be independent so I can fit in the recent part of the context window WHAT THE ACTUAL FUCK? 1 comments on Hacker News.
So I just built a system that on pre-push, watch changes to GH actions using CLI and feed errors to Claude. I am cloning the repo in 5 separate editors with a prompt that makes it develop, commit and push working code at all times. It leans heavily on static analysis and linting with Biome to ensure maximum correctness and strong guidelines for testing. Repository is a monorepo which has cohesive services that can be developed independently. Trunk-Based development and changes go straight to production (there's a post-deploy check that runs smoke tests) I'm not sure if anyone else has built something like this, but essentially I can "git clone" a new version of the repository in a different folder and literally multiply myself by just spending a couple minutes creating a prompt 99% of the Job is designing prompts and adjusting the pieces to be independent so I can fit in the recent part of the context window WHAT THE ACTUAL FUCK?
Hacker News story: Full AI-Based Workflow
![Hacker News story: Full AI-Based Workflow]()
Reviewed by Tha Kur
on
July 10, 2025
Rating:
No comments: