Skip to content
cccskills
FreePublished on GitHub

artisan-commands

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

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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 environment 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 environment 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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when reviewing UI for accessibility — WCAG 2.2 AA, keyboard nav, focus, ARIA, contrast, screen-reader semantics — even on 'is this a11y-OK?' or 'mach das barrierefrei'.

The English summary is being prepared. Showing the original description.

event4u-app/agent-config12Updated Oct 20, 2026

Use when defining or auditing the activation event — aha-moment selection, retention correlation, falsifiable definition. Triggers on 'what is our aha moment', 'redefine activation'.

The English summary is being prepared. Showing the original description.

event4u-app/agent-config12Updated Oct 20, 2026

Use when capturing an architectural decision — file naming, next ADR number, Status / Context / Decision / Consequences, index regen; fires even without saying 'ADR'.

The English summary is being prepared. Showing the original description.

event4u-app/agent-config12Updated Oct 20, 2026

Adversarial critique — devil's advocate, stress-test, honest teardown ('poke holes', 'be brutal', 'was hältst du davon'); explicit request only. Routine code or design review → code-review.

The English summary is being prepared. Showing the original description.

event4u-app/agent-config12Updated Oct 20, 2026

Use when reading, creating, or updating agent documentation, module docs, roadmaps, or AGENTS.md. Understands the full .augment/, agents/, and copilot-instructions structure.

The English summary is being prepared. Showing the original description.

event4u-app/agent-config12Updated Oct 20, 2026

Use for an adversarial red-team / blue-team / auditor review of an AI agent's CONFIG + behaviour (rules, skills, MCP, hooks, permissions) — attack-chain → defensive-gap list, not a code audit.

The English summary is being prepared. Showing the original description.

event4u-app/agent-config12Updated Oct 20, 2026

See all skills by event4u-app

Report a problem with this skill