Im folgenden Beitrag findet ihr Bonus Material für meinen Talk „KI schreibt keinen guten Code – Oder doch?“ auf dem WordCamp Leipzig.
Die Folien für den einleitenden Talk über Code Qualität findet ihr auf der Website meines Arbeitgebers, den Coding Pioneers.
Der (leicht gekürzte) initiale Prompt für die Erstellung des Plans
create a plan for a showcase how to set up: * phpcs (wordpress coding standards) * phpstan * eslint * commitlint * a pre commit pipeline * github actions * plugin check (the reusable workflow) * Basic Setup for Playwright * a ddev local test env with the orchestrate workflow form inpsyde/wp-stash as a result i want to have a plan that will do the mentioned stuff. Sort them in a useful order. The plan shall pause after each step, use atomic commits, and continue on my prompt. Verify yourself that everything is working. Also write a list of prerequisities, of what should be preinstalled, if someone will reuse the plan in their projects. The plan shall be a markdown file, commited to the repository. Each step shall also get a tag, so that checking out intermediate steps is easier to follow. Contrary to my usual config, i want you to create a *_de.md and a *_en.md, so two language versions of the plan. And depending on the plan i will have you run, I want you to reply in the corresponding language, and overruling any global settings that might exist.