code-style-and-static-analysis

name	code-style-and-static-analysis
description	Use when running or fixing code style and static analysis for a Canyon GBS app — the `composer format` / `lint` / `checks` scripts and the tools behind them (PHP CS Fixer, Prettier including Blade, PHPStan/Larastan, Rector, Laravel IDE Helper). Trigger whenever you need to format code, resolve a style or static-analysis failure, run the pre-completion checks before finishing a change, or regenerate IDE helper files after model or schema changes. Do not use for: writing tests (use `writing-tests`) or authoring guidelines and skills (use `authoring-agent-guidance`). For editor/IDE setup, see the app's local-setup docs rather than this skill.
user-invocable	false
license	Elastic-2.0
metadata	{"author":"canyongbs"}

Code Style & Static Analysis

Every change must pass the same checks CI runs before it is considered complete. Apply style fixes with composer format, then run composer lint (PHPStan/Larastan) and resolve everything it reports — never leave violations for CI. Because composer checks is just format-dryrun + lint, running format (which writes the fixes) and then lint covers the same ground without re-checking formatting you just applied — do not run followed by .