production-audit

Analyze git history, configuration, and CI status to score PHP/Laravel production readiness.

Updated Jan 6, 2023
One-click install
npx skills add https://github.com/pekral/phpstan-rules --skill production-audit-pekral
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: production-audit
Source: https://github.com/pekral/phpstan-rules/tree/main/.claude/skills/production-audit
Command: npx skills add https://github.com/pekral/phpstan-rules --skill production-audit-pekral

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the uncertainty of pre-release deployments by providing a structured, evidence-based audit of your codebase, configuration, and CI status to identify potential production failures before they happen.

Core Features & Use Cases

  • Risk Assessment: Evaluates runtime, auth, data integrity, and observability boundaries to catch common production pitfalls.
  • Actionable Verdicts: Provides a clear ship/block decision based on a 0-100 readiness score with specific, concrete fixes for every identified blocker.
  • Use Case: Before merging a critical feature branch, run this audit to ensure all new migrations are reversible, secrets are not exposed, and critical paths are covered by tests.

Quick Start

Use the production-audit skill to assess the readiness of the current branch and provide a ship or block recommendation.

Frequently Asked Questions about production-audit

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

FAQPage Schema
How do I assess Laravel production readiness before a deployment?

Assess Laravel production readiness by analyzing git history, configuration files, and CI status to generate a scored audit report with actionable remediation steps and a clear ship or block decision.

What is a pre-release audit for PHP codebases?

A pre-release audit for PHP codebases is an evidence-based evaluation of runtime, auth, data integrity, and observability boundaries to identify potential production failures before merging or deploying.

Can I check if Laravel migrations are reversible before shipping?

Yes, you can check migration reversibility by running a production readiness audit that evaluates data integrity boundaries and flags missing rollback paths as blockers in the generated report.

How do I get a ship or block decision for my feature branch?

Get a ship or block decision by running a production audit that scores your codebase from 0 to 100 based on git history, configuration, and CI status, providing specific fixes for every identified blocker.

Does the production audit require write access to my repository?

No, the production audit requires only read-only access to the working tree and git logs to evaluate configuration files, CI status, and codebase boundaries without modifying your repository.

What are the limitations of automated deployment readiness checks?

Automated deployment readiness checks are limited to analyzing git history, configuration files, and CI status, meaning they evaluate static codebase boundaries but do not execute runtime tests or simulate live traffic.