quality-checks — Claude Code skill: PHP code quality checks
Runs PHP-CS-Fixer for code style, PHPStan for static analysis, and type checking. Use before committing or when CI quality checks fail.
MIT ★ 234 updated 2026-10-05
npx skills add dev-toolings/superpowers-symfony --skill quality-checks -a claude-codeWhat quality-checks does
This skill automates code quality enforcement in Symfony projects. It detects configuration files (.php-cs-fixer.dist.php, phpstan.dist.neon), runs the style fixer in dry-run mode with a diff, applies fixes, then runs PHPStan at the configured level and addresses type errors.
The skill works with your project's tools—Docker or host environment. It enforces three constraints: does not raise PHPStan level or add baseline entries to hide errors, keeps style-only changes separate from behavior changes, and requires a written reason before silencing any error.
Output shows which commands ran and their results, lists fixes applied (style separate from types), and flags remaining findings that need a decision.
What it helps with
- Fix code style violations before committing
- Identify and resolve type errors in PHP code
- Diagnose why a CI quality job failed
- Configure PHPStan and PHP-CS-Fixer in a Symfony project
Example prompts for the agent
- Check code quality before opening a pull request
- Run quality-checks and fix all PHPStan type errors it reports
- Apply code style and run tests after analysis passes
How to install quality-checks
1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill quality-checks -a claude-code2Manually: put the files in place
~/.claude/skills/quality-checks/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/quality-checks/
1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill quality-checks -a codex2Manually: put the files in place
.agents/skills/quality-checks/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill quality-checks -a cursor2Manually: put the files in place
.cursor/skills/quality-checks/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dev-toolings/superpowers-symfony content/skills/quality-checks2Manually: put the files in place
.github/skills/quality-checks/SKILL.md1Skills CLI (Vercel)
npx skills add dev-toolings/superpowers-symfony --skill quality-checks -a gemini-cli2Platform CLI
gemini skills install https://github.com/dev-toolings/superpowers-symfony --path content/skills/quality-checksManually: put the files in place
.devin/skills/quality-checks/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about quality-checks
How do I install quality-checks in Claude Code?
Run npx skills add dev-toolings/superpowers-symfony --skill quality-checks -a claude-code, then open ~/.claude/skills/quality-checks/SKILL.md.
What does quality-checks do?
Runs PHP-CS-Fixer to fix code style, PHPStan to analyze and check types, then runs tests. Displays diffs and errors that need resolution.
Can I raise the PHPStan level if the check fails?
No, the skill prevents that. Instead, fix the type errors in your code or add a justified ignore comment.
Source text
SKILL.md · MIT
--- name: quality-checks description: "Run code quality tools: PHP-CS-Fixer for style, PHPStan for static analysis, and type safety checks" capabilities: [read, search, edit, shell] tags: [workflow, quality] # projected by `bun run build` — do not edit by hand allowed-tools: - Read - Glob - Grep - Write - Edit - Bash --- # Quality Checks (Symfony) ## Use when - Before committing or opening a pull request. - Setting up or tuning PHP-CS-Fixer or PHPStan in a Symfony project. - A CI quality job fails and the cause must be found and fixed. ## Default workflow 1. Detect the tools and configuration files present (`.php-cs-fixer.dist.php`, `phpstan.dist.neon`). 2. Run the style fixer in dry-run with a diff first, then apply it. 3. Run PHPStan at the configured level and fix the reported types. 4. Run the test suite last, after style and analysis are green. ## Guardrails - Do not raise the PHPStan level or add baseline entries to make a run pass. - Keep style-only changes in their own commit, apart from behavior changes. - Do not silence an error with an ignore rule without a written reason. - Use the runner the project uses (Docker or host), from the runtime context. ## Progressive disclosure - Use this file for execution posture and risk controls. - Open references when deep implementation details are needed. ## Output contract - The commands run and their result. - The fixes applied, style separated from types. - Remaining findings that need a decision. ## References - `reference.md`
© dev-toolings · MIT · dev-toolings/superpowers-symfony