laravel-zero-cli
Automates testing, linting, building, and release management for Laravel Zero CLI projects.
Install
mkdir -p .claude/skills/laravel-zero-cli && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15155" && unzip -o skill.zip -d .claude/skills/laravel-zero-cli && rm skill.zipInstalls to .claude/skills/laravel-zero-cli
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Core workflows for the Black Labs Laravel Zero CLI (build, test, lint, release helpers)Key capabilities
- →Install project dependencies using Composer
- →Run all tests or single tests using Pest
- →Lint and format code using Pint
- →Build Phar archives with a specified version
- →Create release branches by merging issue branches and tagging
- →Deploy to production by merging to `forge-production` and updating versions
How it works
This skill provides specific commands and conventions for managing Laravel Zero CLI projects, covering installation, testing, linting, building, and release workflows.
Inputs & outputs
When to use laravel-zero-cli
- →Run linting and tests before packaging
- →Create a release branch from multiple issue branches
- →Deploy a release branch to production
- →Build a production Phar
About this skill
Use this skill when working in this repo or similar Laravel Zero CLI projects.
Commands
- Install:
composer install - Test (full):
php blacklabs testor./vendor/bin/pest - Test (single):
./vendor/bin/pest tests/Feature/CreateReleaseBranchTest.php --filter="works in a dummy git repo" - Lint/format:
./vendor/bin/pint - Build Phar:
php blacklabs app:build --build-version=<vX.Y.Z>
Release/Deploy flows
- Create release branch:
php blacklabs create-release-branch <level|vX.Y.Z[-N]> <issue1,issue2>(merges issue branches, tags via npm, pushes branch+tags, may callgh pr create). - Deploy to production:
php blacklabs deploy-to-production [release/...](confirmsforge-production, merges to prod, bumps npm version, merges prod -> dev, deletes release branch). - Packagist deploy:
php blacklabs app:deploy(must be on a clean default branch in the upstream repo; runs tests, builds Phar, tags/pushes).
Conventions
- Branches: issue branches start with issue number; release branches
release/<version>/<issues>; production branchforge-production; primary dev branchdev. - Versioning: npm-based tags
vX.Y.Z[-N]; tags pushed. - Use
App\Services\RunsProcessesfor shelling out; merge conflicts handled viaMergesBranches(pauses for manual resolution).
Prompts to offer
- "Run lint + tests before packaging": run pint then pest, then
app:build. - "Create release branch for issues 123,456 as preminor": call
create-release-branch preminor 123,456. - "Deploy release branch to prod and sync dev": call
deploy-to-production <branch>. - "Reload and manage skills each session":
/skills reloadthen add/remove as needed.
When not to use it
- →When working on projects that are not Laravel Zero CLI based
- →When the project does not use Pest for testing
- →When the project does not use Pint for linting
Limitations
- →Packagist deployment requires being on a clean default branch in the upstream repository
- →Merge conflicts are handled via `MergesBranches` which pauses for manual resolution
- →The skill assumes the use of npm-based tags for versioning
How it compares
This workflow automates complex release and deployment processes, such as merging multiple issue branches and handling versioning, which would otherwise be manual and error-prone.
Compared to similar skills
laravel-zero-cli side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| laravel-zero-cli (this skill) | 0 | 4mo | No flags | Intermediate |
| magerun-release | 1 | 5mo | No flags | Intermediate |
| release-minor | 1 | 2mo | No flags | Intermediate |
| github-release-management | 4 | 6mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
magerun-release
netz98
Technical release process for n98-magerun2
release-minor
knuckleswtf
Automates the process of tagging a new minor release for Scribe by analyzing commit messages, updating the changelog, and creating a GitHub release.
github-release-management
ruvnet
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management
agent-release-swarm
ruvnet
Agent skill for release-swarm - invoke with $agent-release-swarm
release
ziggy42
Use this skill when the user wants to cut a new release.
release-branch
mono
Create a release branch for SkiaSharp. Use when user says "release X", "start release X", "create release branch for X", "I want to release", or "release now". This is the FIRST step of releasing - creates branch and pushes to trigger CI. Can auto-detect next preview version from main branch.