Say what you will about "Agentic Coding". But it deserves credit where credit is due.
I'm not the fanniest of fanboys there is for AI agent-assisted coding. Not hardly. I have an AGENTS.md in every single project. The directives in it strictly forbid agents from ever presenting unsolicited diffs to change my code. If any ever do and I haven't explicitly requested them, I reject them.
That said, the deafening crickets from this post led me to discover a valuable use case for Cline (formerly Claude Dev) [1]. Namely: verifying the clarity and correctness of usage instructions.
I copied and pasted the usage instructions that I provide on the com.lingocoder:mrjar plugin's Git Hub Pages [2]
Apart from me having to tell it where to find a Gradle binary, the agent understood the usage instructions without me having to change anything in them.
That gives me confidence that the steps themselves are clear. And, if followed faithfully, they result in Gradle successfully building a project that applies the plugin. The example configurations in the instructions produce a successfully initialized project.
Most overextended software engineers who want reproducible builds, would appreciate the value in handing off that kind of proofreading task to a robut.
Say what you will about "Agentic Coding". But it deserves credit where credit is due.
I'm not the fanniest of fanboys there is for AI agent-assisted coding. Not hardly. I have an AGENTS.md in every single project. The directives in it strictly forbid agents from ever presenting unsolicited diffs to change my code. If any ever do and I haven't explicitly requested them, I reject them.
That said, the deafening crickets from this post led me to discover a valuable use case for Cline (formerly Claude Dev) [1]. Namely: verifying the clarity and correctness of usage instructions.
I copied and pasted the usage instructions that I provide on the com.lingocoder:mrjar plugin's Git Hub Pages [2]
Apart from me having to tell it where to find a Gradle binary, the agent understood the usage instructions without me having to change anything in them.
That gives me confidence that the steps themselves are clear. And, if followed faithfully, they result in Gradle successfully building a project that applies the plugin. The example configurations in the instructions produce a successfully initialized project.
Most overextended software engineers who want reproducible builds, would appreciate the value in handing off that kind of proofreading task to a robut.
[1] https://g2ww.short.gy/IfSoInClined [2] http://lingocoder.com/mrjar/