A lint rule is only enforceable if the agent can't edit the rule. Prompt files are guidance because the model can ignore them. A config file is just another file in the repo and an agent can find ways to bypass that. I've seen my agent code around it or quietly loosen the config instead of fixing the code.
My solution was putting the hook and lint configuration where the agent can't write to it. That was more effort to set up, but it seems to work.
Because consistency is still considered a quality rubric ?
Absolutely, I could touch on that in the article more.
A lint rule is only enforceable if the agent can't edit the rule. Prompt files are guidance because the model can ignore them. A config file is just another file in the repo and an agent can find ways to bypass that. I've seen my agent code around it or quietly loosen the config instead of fixing the code.
My solution was putting the hook and lint configuration where the agent can't write to it. That was more effort to set up, but it seems to work.
Great consideration to make, those rule sets should absolutely require at least a confirmation from a human to change.