Post #3606817

2026-07-05 15:12 UTC

@elazar@phpc.social @jrf_nl@phpc.social The best way to enforce things, even according to Claude’s docs, is to use static analysis and coding standards tools as part of pre-commit hooks. This will restrict the AI from making the commit until the issues are fixed. It sucks, though, because it’s a waste of tokens for it to churn like that.

Replies (2)

@ramsey@phpc.social 2026-07-05 15:16

@elazar@phpc.social @jrf_nl@phpc.social It also has to be part of an enforced hook because, if you leave it up to the AI to remember to always run them before committing, there will be many times they’ll just “forget” and commit straight away. When called out, it’s an “Oh, yeah! I was supposed to do that!” moment. They cannot be relied on to be deterministic. They’re still just advanced auto-complete.

Open ##3606816
@elazar@phpc.social 2026-07-05 15:16

@ramsey@phpc.social @jrf_nl@phpc.social I do appreciate the validation that AI has brought to the best practices that have become established over the last two decades or so: the importance of context in architecture and implementation, documentation and automated tests as first-class deliverables, static analysis tools, etc. I think it's given me a new appreciation of the fact that what makes developing software easier for us also makes it easier for AI agents.

Open ##3606822