Integrations: AI Agents, CI, Git Hooks and Editors
A coding standard that runs only when someone remembers to run it will slowly fade. DressCode can run in four
places, from the moment code is written to the moment it is merged, and it does a different job in each of them. All four read the
same dresscode.neon, so the agent, the editor, the hook and the server hold the code to the same standard.
Four Places, One Configuration
| where | when it runs | what it does | how to set it up |
|---|---|---|---|
| AI agent | after every edit of a PHP file | fixes the file and tells the agent what changed in it | AI Agents |
| editor | when you save a file | formats the file the way dresscode fix would |
Editors and IDEs |
| Git hook | before a commit | checks only the files that go into the commit, and prints nothing while they are clean | Git Hooks |
| CI | on every push | runs dresscode check, and a finding fails the job; on GitHub, findings appear right at their lines in the pull
request |
Continuous Integration |
The first two fix the code as it is written, so most findings never reach anyone. The other two only check: they stop code that
slipped through and leave the fix to the developer. Every place needs DressCode installed and a dresscode.neon in the
root of the project. Getting Started shows the
installation, and Format Your Code Step by Step shows how to write the
configuration from the code you already have.
Which One First
If you set up only one, set up CI. It is the only place nobody can skip: a hook can be bypassed with
git commit --no-verify, and an editor is set up on each machine separately, while CI checks every push from everyone.
Then I would add format on save in the editor, because with it you never see most findings at all.
If an AI agent writes part of your code, give it the plugin as well. An agent writes fast and in its own way, and without the plugin you would fix its style after every task. With the plugin, DressCode fixes each file right after the edit, and the agent learns what changed, so its next edit does not fail on text that is no longer there.
The Git hook is the last step, for a team that wants to catch a finding before it reaches the server. It costs nothing while the code is clean, because then it prints nothing.