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

pre-release

Run Rector, Pint, Pest, and PHPStan checks before release tagging.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures release readiness by executing a comprehensive pre-release quality gate before tagging, catching regressions, drift, and documentation staleness across code and docs.

Core Features & Use Cases

  • Runs Rector to normalize code, Pint for style, Pest for tests, and PHPStan for static analysis.
  • Audits README and the .ai/ docs for freshness to keep downstream guidance accurate.
  • Executes benchmark harnesses to detect performance regressions and gate shipping readiness.
  • Use Case: Maintainers trigger the pre-release workflow before pushing a release to ensure CI green, accurate release notes, and validated benchmarks.

Quick Start

Run the pre-release checklist before tagging a release.

Frequently Asked Questions about pre-release

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

FAQPage Schema
How do I automate a pre-release quality gate for PHP projects?▼

Automating a pre-release quality gate involves running Rector for code normalization, Pint for styling, Pest for tests, and PHPStan for static analysis. This ensures code readiness and prevents regressions before tagging a release.

How do I detect performance regressions before tagging a release?▼

To detect performance regressions before tagging, you execute benchmark harnesses as part of a pre-release workflow. This validates shipping readiness by gating releases on benchmark performance metrics.

What is included in a PHP release readiness checklist?▼

A PHP release readiness checklist includes running static analysis with PHPStan, executing Pest tests, normalizing code with Rector, and auditing documentation freshness to ensure accurate downstream guidance.

Can I use Rector and PHPStan together in a continuous integration workflow?▼

Yes, Rector and PHPStan can run together in a continuous integration workflow. Rector normalizes code structure while PHPStan performs static analysis, combining to provide strong validation and deterministic quality gating.

How do I audit documentation freshness before a release?▼

Auditing documentation freshness before a release involves checking README and .ai/ docs directories. This ensures downstream guidance remains accurate and prevents documentation staleness across code and docs.

When should I run a pre-release code quality check?▼

You should run a pre-release code quality check when applying release tagging, pushing tags, or requesting release checklists. This ensures deterministic steps and strong validation are completed before shipping.

Related Skills

Explore More Software Engineering Skills→
morodomimorodomi
8

laravel-quality

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

Community
Intermediate
AndrewDrygaAndrewDryga
28

release

Create semantic version tags from changelogs and push them to Git.

Community
Advanced
sambersamber
2.9k

golang-benchmark

Design and execute Go benchmarks with b.Loop and benchstat comparisons.

Community
Advanced
iamzifeiiamzifei
799

money-quality

Automate linting, testing, performance, and security checks before release.

Community
Advanced