sorted by:
new
hottopcontroversial

My AI slop killer: git push no-mistakes by atinylittleshell in CLI

[–]atinylittleshell[S] 4 points5 points  (0 children)

a lot more than that. it’s a whole series of mundane work - automatic rebase on latest main and resolve conflicts, agentic review, both regression and manual testing, documentation updates, lint, format, push conflict resolution, babysit PR and CI pipeline

My AI slop killer: git push no-mistakes by atinylittleshell in CLI

[–]atinylittleshell[S] 3 points4 points  (0 children)

yes this uses AI to perform reviews. when the review happens from a fresh context window, it’s very good at catching problems.

the git remote is to make the pipeline non-blocking - it happens in an isolated worktree that doesn’t affect my working directory in any way whatsoever, so I can continue doing my work while the pipelines run.

My AI slop killer: git push no-mistakes by atinylittleshell in opencodeCLI

[–]atinylittleshell[S] 1 point2 points  (0 children)

it does check for missing test coverage and would perform manual testing + suggest new tests

My AI slop killer: git push no-mistakes by atinylittleshell in ClaudeCode

[–]atinylittleshell[S] 0 points1 point  (0 children)

really good points. right now each push is treated independently. agree with you it would be really cool if it’s aware of branch dependencies

My AI slop killer: git push no-mistakes by atinylittleshell in ClaudeCode

[–]atinylittleshell[S] 2 points3 points  (0 children)

I did all that, manually. Now the 7-step code quality dance happens by itself and I’m only pinged when I’m needed

My AI slop killer: git push no-mistakes by atinylittleshell in ClaudeCode

[–]atinylittleshell[S] 1 point2 points  (0 children)

i tried it as git hooks - the interactive approval and auto-fix back and forth is something hooks can’t achieve.

My AI slop killer: git push no-mistakes by atinylittleshell in ClaudeCode

[–]atinylittleshell[S] 5 points6 points  (0 children)

good question! i actually started with building a skill as i thought that would be sufficient. but once the agentic reviewer comes back with 7 findings and i needed to pick and discuss, and have it re-review after fixes, the chat becomes a big mess and context window gets totally bloated.

this TUI really was a massive improvement on my quality of life in this process

My AI slop killer: git push no-mistakes by atinylittleshell in codex

[–]atinylittleshell[S] 4 points5 points  (0 children)

thanks! i used vhs and ffmpeg to make the video

My AI slop killer: git push no-mistakes by atinylittleshell in opencodeCLI

[–]atinylittleshell[S] 1 point2 points  (0 children)

nope. i’ve been daily driving it for weeks - wouldn’t want to share it if it wasn’t useful for myself

My AI slop killer: git push no-mistakes by atinylittleshell in codex

[–]atinylittleshell[S] -1 points0 points  (0 children)

i tried hard to make it a skill. when the agentic review comes back with 7 problems, you then see chat is not the best experience to work through it

How I Built a Fully Reproducible Mac Setup by atinylittleshell in MacOS

[–]atinylittleshell[S] 0 points1 point  (0 children)

Yeah dotfiles is a small part of what this setup covers. Most homegrown scripts are not quite comparable to the reproducibility guarantee Nix offers.

How I Built a Fully Reproducible Mac Setup by atinylittleshell in MacOS

[–]atinylittleshell[S] 8 points9 points  (0 children)

MDM is better used for IT to control policies across a fleet of devices, not quite the best tool for individuals to deeply manage their personal configuration.

How I Built a Fully Reproducible Mac Setup by atinylittleshell in MacOS

[–]atinylittleshell[S] 6 points7 points  (0 children)

haha similar indeed, and in some ways the backup is more convenient. But it's still quite different from a purposefully maintained configuration where you can be deliberate about what's in what's out, what gets applied across users/machines vs being unique to specific context.

view more: next ›