skills.rest
SanderMuller
SanderMullerCOMMUNITY
Explore all skills by this author →
𝕏@sander_scodeGitHub

backend-quality

Run Pint and PHPStan checks plus tests for PHP projects.

214|2|Updated Apr 2, 2026
Search Tags:#testing#php#code-quality#static-analysis#phpstan#lint#pint
One-click install
npx skills add https://github.com/SanderMuller/laravel-fluent-validation --skill backend-quality
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-quality
Source: https://github.com/SanderMuller/laravel-fluent-validation/tree/main/.ai/skills/backend-quality
Command: npx skills add https://github.com/SanderMuller/laravel-fluent-validation --skill backend-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backend code quality checks aimed at catching issues early by automating linting, style, and static analysis as part of the development workflow.

Core Features & Use Cases

  • Tier 1: Pint (code style) and related tests run after every change to PHP files.
  • Tier 2: PHPStan (static analysis) and the full test suite run at completion to validate the entire codebase before PRs.
  • Use Case: Teams enforcing consistent style and thorough analysis before merges.

Quick Start

Activate this skill and run Tier 1 checks after each PHP change, then run Tier 2 checks at completion.

Frequently Asked Questions about backend-quality

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate PHP code quality checks for Laravel projects?▼

A two-tier backend quality workflow catches issues early: Tier 1 runs Pint and related tests after every PHP file change, while Tier 2 executes PHPStan and the full test suite at completion to validate the codebase for pull requests.

Do I need PHPStan and Pint installed to run automated PHP linting and static analysis?▼

Yes, Pint, PHPStan, and the full test suite must be available in the project's vendor bin directory. The automated quality checks require these specific tools to execute linting, static analysis, and testing successfully.

What is the best way to enforce consistent code style before merging PHP code?▼

Use a two-tier approach: run Pint after every PHP file change during development for immediate style feedback, then execute PHPStan and the full test suite at completion to ensure code style, static analysis, and test coverage before merging.

How does the two-tier PHP quality check process work?▼

Tier 1 runs Pint and related tests after every PHP file change during development, while Tier 2 executes PHPStan and the full test suite at completion to validate the entire codebase before merging.

Can I use this automated static analysis workflow for non-Laravel PHP projects?▼

The workflow is applicable for Laravel and general PHP projects. It integrates with common PHP tooling to ensure code style, static analysis, and test coverage before merging, provided Pint, PHPStan, and the test suite are available in the project's vendor bin.

Why run Pint during development and PHPStan only at completion?▼

Running Pint during development provides fast style feedback after each change, while PHPStan at completion performs deep static analysis across the entire codebase. This separation prevents slow static analysis from interrupting active development.

Related Skills

Explore More Software Engineering Skills→
morodomimorodomi
8

laravel-quality

Run Pest, Larastan, and Pint quality checks on Laravel projects.

Community
Intermediate
roycolumbia-coderoycolumbia-code

gsd-ship

Automates GitHub pull request creation, review triggering, and merge tracking.

Community
Intermediate
FlexNetOSFlexNetOS

alpha

Execute predefined test scenarios in CI/CD environments.

Official
Basic
DevanBDevanB

Global Coding Style

Enforce global coding style across PHP and TypeScript/JavaScript projects.

Community
Basic