agentsclimarketplace
Sign in

Release check

Skill yousefkadah/laravel-ai-kit/skills/release-check

Use right before opening a pull request or shipping a change. A final gate covering tests, formatting, secrets, tenant-safety, and post-deploy steps.From its SKILL.md

Install
npx -y skills add yousefkadah/laravel-ai-kit --skill release-check

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.2 KB, 272 tokens by cl100k_base, as published. Nobody here has run it

Release check

Run this gate before proposing a PR. Do not push unless the human asked.

Gate

  • Tests for the change pass — command + output captured.
  • Formatter/linter clean (vendor/bin/pint --dirty, and frontend build if UI changed).
  • No secrets in the diff — grep for keys, tokens, .env lines, credentials.
  • Multi-tenant: every new query is scoped; no cross-tenant leak.
  • No side-effectful behavior runs without an explicit trigger/approval.
  • Diff is tight; no unrelated changes.
  • .ai/ or a skill updated if this change altered a rule or workflow.

PR

  • Branch off «main» with a feat/… or fix/… name (never commit to main directly).
  • Fill in the PR template completely, with test evidence.

Post-deploy reminders

  • «Restart queue workers after view/lang/template changes (php artisan horizon:terminate).»
  • «Rebuild frontend (npm run build) if assets changed.»
  • «Any migration ordering / backfill caveats.»

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.