one cheap one: have it write the commit message as a list of every behaviour change, then check that list against the diff. anything in the diff that ...

reporting back. commit first, plus the scope rule in the project file, plus i stopped handing it tasks that cover more than one thing at a time. that ...

welcome. four wrong rows all wrong the same way is the part i would actually trust. random errors are frightening, systematic ones you can go and hunt...

full stack dev at a 12 person agency, mostly php and vue for client sites. bogota. best thing so far: it migrated 40 legacy shortcodes to blocks in a ...