laravel-verification
by affaan-mlaravel-verification is a pre-PR and pre-deploy workflow for Laravel projects. Use this laravel-verification skill to run install, environment, Composer, linting, tests, security, and release readiness checks in sequence with less guesswork.
This skill scores 78/100, which means it is a solid directory listing candidate for users who want a Laravel preflight verification workflow instead of a generic prompt. The repository shows a real, ordered process for environment checks, Composer validation, linting/static analysis, tests with coverage, security review, and deployment readiness, so agents can follow it with relatively low guesswork. It is still somewhat limited by the lack of supporting files and install automation, so users should view it as a workflow guide rather than a heavily packaged tool.
- Clear Laravel-specific trigger conditions: pre-PR, post-refactor, and pre-deploy verification.
- Concrete phased workflow with sequential gates from environment checks through deployment readiness.
- Operational commands and checks are included, which improves agent triggerability and execution confidence.
- No install command or support files are provided, so adoption requires manual setup and reading the SKILL.md closely.
- Experimental/test signals and the absence of scripts or references may reduce trust for teams wanting a more packaged or validated skill.
Overview of laravel-verification skill
What laravel-verification does
The laravel-verification skill is a pre-PR and pre-deploy verification workflow for Laravel projects. It helps you run the right checks in the right order—environment, Composer, linting, static analysis, tests, security, and release readiness—so you catch breakage before it reaches staging or production.
Who it is for
Use the laravel-verification skill if you work on a Laravel app and need a repeatable verification pass for refactors, dependency upgrades, CI failures, or release prep. It is especially useful for agents and developers who want a structured laravel-verification guide instead of improvising a generic prompt.
What makes it useful
The main value is sequencing. The skill does not just list checks; it gates later steps behind earlier ones, which reduces wasted work and makes failures easier to interpret. That matters when you need laravel-verification for Workflow Automation because a broken environment, autoload issue, or config mismatch should stop the run early.
How to Use laravel-verification skill
Install the laravel-verification skill
Use the directory’s install flow to add the skill, then load it in the workspace where you want verification behavior to apply. For this repo, the baseline install command is:
npx skills add affaan-m/everything-claude-code --skill laravel-verification
After install, confirm the skill is available in the current project context before asking for a verification pass.
Read the right files first
Start with SKILL.md because it contains the actual workflow, then inspect the surrounding skill folder for any linked context if present. In this repository, SKILL.md is the primary source and there are no helper scripts or reference folders, so the file itself is the thing to trust first.
Focus on:
When to UseHow It WorksPhase 1: Environment ChecksPhase 1.5: Composer and Autoload
These sections tell you where the laravel-verification install and usage boundaries really are.
Shape a strong request
The skill works best when you give it a concrete target, not a vague “check my app.” Include the environment, the change type, and the release risk. For example:
- “Run the
laravel-verificationskill against this Laravel app after a PHP upgrade.” - “Use
laravel-verificationto verify staging readiness for this branch.” - “Apply the
laravel-verification guideto a production deploy candidate and report blockers only.”
Add the tools you actually use, such as Sail, PHPUnit/Pest, PHPStan, Pint, or your deployment pipeline, so the output matches your stack.
Follow the workflow order
A good run starts with environment checks and Composer validation, then moves to linting/static analysis, then tests, then security and deployment readiness. Do not ask the model to jump straight to test output or deployment advice if the base environment may be broken. That sequencing is the core of the laravel-verification usage pattern and is what makes the skill more actionable than a loose prompt.
laravel-verification skill FAQ
Is laravel-verification only for Laravel apps?
Yes. The skill is designed around Laravel-specific checks like php artisan, Composer autoloading, and deployment readiness for Laravel conventions. If your project is not Laravel-based, a generic verification prompt will fit better.
How is this different from a normal prompt?
A normal prompt often produces an unstructured checklist. The laravel-verification skill gives you a disciplined order of operations: verify the environment, confirm autoloading, lint, analyze, test, then review security and release gates. That improves reliability when you need consistent results across branches or agents.
Do beginners need to understand every tool first?
No, but they should know what environment they are in and what changed. The skill is useful even if you do not fully understand PHPStan or deployment readiness yet, because it turns the verification job into a sequence you can follow and inspect.
When should I not use this skill?
Do not use laravel-verification for exploratory coding, UI brainstorming, or feature ideation. It is a verification skill, not a build-a-feature skill. It also adds less value if you only need one isolated check, such as a quick lint run, rather than a full release gate.
How to Improve laravel-verification skill
Give the skill better starting context
The biggest quality boost comes from telling the skill what changed and what risk you care about. Compare:
- Weak: “Verify my Laravel project.”
- Strong: “Verify this Laravel app after changing queue workers, env values, and a database migration; surface anything blocking deployment.”
The second version helps the laravel-verification skill prioritize the right checks and explain failures in deployment terms.
Match the checks to your stack
If you use Sail locally, say so. If you use Pest instead of PHPUnit, or PHPStan at a specific level, include that. Strong inputs reduce false assumptions and make the laravel-verification usage output align with your actual repo instead of an imagined Laravel default.
Ask for blockers, not noise
For decision-making, ask for the issues that would stop merge or deploy. This skill is most useful when it distinguishes hard failures from optional cleanup. If you want a tighter result, request:
- blocking issues only
- suggested next checks in order
- deploy readiness verdict
- missing environment or config keys
That keeps the laravel-verification guide focused on action, not narration.
Iterate after the first pass
If the first run finds a failure, rerun with the exact failing command, the environment you are in, and the branch goal. For example, provide the failing composer validate output or the specific test suite that regressed. The more precise your follow-up, the better the next verification pass will isolate root cause and next steps.