Michael
3.3K posts











“The CLI is the Stone Age from two months ago. GUIs are back.” You heard it here first. @nateliason live from @every's Vibe Code Camp:


Hired my first employee today

I'm excited to share a Claude Code enhancement I've been working on. It dramatically expands Claude's autonomy once you've created a PR, accelerating your work as a solo dev or small team without getting reckless. Problem: The built-in Claude Code Github PR Review leaves a ton of feedback which you then have to comb through, decide what to address, and feed your priorities back into Claude Code. Solution: dangerously-skip-review gives Claude permission to analyze its own feedback, implement the necessary fixes, and create follow up issues to address after the PR is completed. With dangerously-skip-review, here's what happens once you open a PR: 1. Claude will review the PR in detail. 2. Claude will evaluate that review to identify must-fix items and issues that can be addressed later. 3. Claude will solve the must-fix items. 4. Claude will create follow-up issues to be addressed after the PR is merged. 5. Once the PR is merged, Claude will evaluate the follow up issues, decide if they're worth implementing, and if they are, code them up and open new PRs. If they aren't, Claude will close them with an explanation. 6. The cycle repeats for the new PRs. WARNING: This might eat through your usage limits depending on your repository and plan level, and obviously it could break things. Use it responsibly. If you want to try it out, install the Claude Code Github Actions for your repo (/install-github-app in claude code) then run: npx dangerously-skip-review Let me know what you think! PRs welcome for any improvements.



































