agentsclimarketplace

Artisan commands

Skill event4u-app/agent-config/dist/agent-src/skills/artisan-commands

Universal AI Agent OS — audited skills, governance rules, replayable state. One contract, every host agent.

Install
npx -y skills add event4u-app/agent-config --skill artisan-commands

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

  • 7 stars7 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.

What its author says it does

Copied from the file, not written here

Use when creating or modifying Artisan commands. Covers clear signatures, safe execution flow, helpful output, and project conventions for console tooling.

SKILL.md

2.6 KB, as published. Nobody here has run it

artisan-commands

When to use

Use when creating or modifying Laravel Artisan commands — maintenance scripts, imports/exports, batch processing, repair/cleanup, scheduled tasks, developer utilities.

Do NOT use when:

  • Writing queue jobs (use jobs-events skill)
  • Writing scheduled task config (use laravel-scheduling skill)

Procedure: Create an Artisan command

Step 0: Inspect

  1. Check existing commands — match naming, signature style, output format.
  2. Determine audience: developer, support, operations, cron, or scheduler.
  3. Determine if interactive or automated.
  4. Identify related services — commands orchestrate, not own business logic.

Step 1: Scaffold

  1. Create command class in app/Console/Commands/ or module App/Commands/.
  2. Name: {domain}:{action} — e.g. users:cleanup, orders:sync.
  3. Define arguments (required) and options (toggles/filters) explicitly.

Step 2: Implement handle()

  1. Validate preconditions (environment, input, dependencies).
  2. Call service/action for business logic.
  3. Report progress and results via console output.
  4. Return appropriate exit code.

Step 3: Safety checks

  • Destructive? → Add --force flag + confirmation.
  • Scheduled? → Ensure non-interactive, idempotent, loud failures.
  • Long-running? → Use chunking/cursors, progress bar.
  • Production? → Add env check if needed.

Step 4: Test

  • Assert exit codes, console output, side effects, option behavior.
  • Use $this->artisan() in Pest tests.

Conventions

→ See guideline php/artisan-commands.md for full conventions.

Output format

  1. Artisan command class with signature, description, and handle method
  2. Registration in service provider or auto-discovery
  3. Example usage shown in a code comment

Gotcha

  • $this->info() is suppressed in quiet mode — use $this->line() for critical info.
  • Always add --force for destructive commands — never delete data without confirmation.
  • Add env checks for production commands.

Do NOT

  • Do NOT run destructive operations without --force confirmation.
  • Do NOT use $this->ask() for non-interactive commands (cron/queue).
  • Do NOT put business logic in commands — delegate to services.

Auto-trigger keywords

  • artisan command
  • console command
  • CLI command
  • command signature

Keep looking

Skills are one crate of 328,083. 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.