Skip to main content
skill CX Codex

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

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add dev-toolings/superpowers-symfony --skill quality-checks -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/quality-checks/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/quality-checks/

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

Similar skills

All skills for Code review and refactoring →

From the same set51

The whole set →
symfony-voters The symfony-voters skill guides Symfony Voter authorization work, from mapping access decisions to testing denied cases. Use it to keep permission checks out of duplicated controller logic. CX Codex +1 ★ 234repo stars writing-plans writing-plans generates structured implementation plans for Symfony features with clear steps, acceptance criteria, and risk mitigations. CX Codex +1 ★ 234repo stars value-objects-and-dtos This skill guides Symfony work with immutable Value Objects and DTOs, covering constructor validation, value equality, and data crossing application boundaries. CX Codex +1 ★ 234repo stars effective-context effective-context is a Claude Code skill that teaches an agent to gather context for Symfony development: versions, error-path files, stack traces, and project constraints. CX Codex +1 ★ 234repo stars strategy-pattern Implements the Strategy pattern in Symfony using tagged services. Helps clean up branching logic when algorithms or providers vary at runtime. CX Codex +1 ★ 234repo stars executing-plans The executing-plans skill guides Claude Code through an approved implementation plan, with test-first steps and a separate commit for each one. Use it for multi-step work or to resume after an interruption. CX Codex +1 ★ 234repo stars twig-components twig-components turns repeated Twig markup into Symfony UX components with props, slots and CVA variants. Handy once the same template chunk starts getting copied around. CX Codex +1 ★ 234repo stars cqrs-and-handlers cqrs-and-handlers implements CQRS in Symfony projects using separate Messenger buses for commands and queries. CX Codex +1 ★ 234repo stars

Project sponsors

Companies that keep this analytics open