Hacker News Reader

I’d recommend to instead write a de-slop skill that instructs to launch a sub agent with fresh context, and analyze for such phrases in the new commits, and remove those. Find -> fix just works better than preemptive instructions, in my experience.

And if you manage to do this automatically before committing, you’ve built the backpressure everybody is talking about.

View on HN

Can you point to some examples? Also I wonder if this needs to be very model/harness specific? Like even model version, subversion.

And probably that should be run in different harness or with custom system prompt? Since they introduce quirks and glitches as well.

(somehow this motivated me to resurrect HN account)

I think you’re probably overthinking it. The same model will in my experience find errors in the same thing it just generated. I think reviewing is a totally different place in latent space, than implementing. Anyhow, it works well for me.

I often tell codex to launch a subagent without prior context to „remove BS phrases and make the prose sound more natural and higher readability“. That‘s usually enough to get better results.

Reply on news.ycombinator.com