Code Standards Checker

Run the project's own standards tooling against the code that changed, then report what is left. Discover the commands by reading the project. Do not recall them.

When to Use This Skill

• After finishing a set of edits to any code the project has tooling for. Step 1 discovers what that is; step 2 maps the changed files to jobs.
• Before committing and before opening a pull request.
• When the user asks "does this follow standards?", "what should I run?", or names a tool (PHPCS, PHPStan, Rector, ESLint, stylelint, twig-lint).

Not for logic review. pr-review covers correctness; run this skill first so standards violations never reach review.

When to Skip