chore(claude): convert commands to SKILL.md format with auto-trigger

Add YAML frontmatter to all 6 project commands so Claude auto-triggers
them based on conversation context rather than requiring explicit /cmd
invocation. Each skill description includes clear trigger signals and
explicit "use proactively" guidance.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: Thomas Laure

.claude/commands/bug-fix.md

@@ -1 +1,14 @@
+---
+name: bug-fix
+description: >
+  Runs the structured 8-step bug fix workflow for Signalist.
+  Trigger this whenever the user describes something that is broken, not working
+  as expected, producing an error, or behaving incorrectly — test failures,
+  exceptions, wrong output, a feature that used to work and no longer does.
+  Trigger even without the word "bug": phrases like "this is broken", "I'm
+  getting an error", "it's not working", "the test fails", "something is wrong
+  with..." are all clear signals. Use this skill proactively for any defect
+  investigation and fix, not just when the user explicitly asks for a bug fix.
+---
+
 Read `.claude/workflows/bug-fix.md` and start the bug fix workflow for: $ARGUMENTS

.claude/commands/hotfix.md

@@ -1,3 +1,16 @@
+---
+name: hotfix
+description: >
+  Runs an expedited minimal hotfix workflow for Signalist.
+  Trigger this when the user describes a critical or urgent issue that needs
+  an immediate, minimal fix — production is broken, a live bug is affecting
+  users, something needs to be patched right now. Key signals: "production",
+  "prod", "urgent", "critical", "hotfix", "emergency", "live issue", "users
+  are affected". Distinct from a regular bug fix: hotfixes are about speed and
+  minimal blast radius, not thorough investigation. Use this skill proactively
+  whenever urgency and minimalism are the priority.
+---
+
 Start an expedited hotfix workflow for the production issue: $ARGUMENTS
 
 This is a HOTFIX — keep changes minimal and focused on the fix only.
@@ -18,7 +31,8 @@ This is a HOTFIX — keep changes minimal and focused on the fix only.
 3. **Minimal fix only**
    - Change the least amount of code necessary
    - No refactoring, no unrelated improvements
-   - If the root cause requires a larger fix, implement a safe temporary workaround and create a follow-up task
+   - If the root cause requires a larger fix, implement a safe temporary
+     workaround and create a follow-up task
 
 4. **Regression test**
    - Write one test that reproduces the bug and passes after the fix
@@ -36,4 +50,5 @@ This is a HOTFIX — keep changes minimal and focused on the fix only.
    - `gh pr create` targeting `master`
    - After merge, monitor logs for 10 minutes
 
-Read `.claude/workflows/bug-fix.md` for the full workflow if the issue requires deeper investigation.
+Read `.claude/workflows/bug-fix.md` for the full workflow if the issue requires
+deeper investigation.

.claude/commands/new-feature.md

@@ -1 +1,14 @@
+---
+name: new-feature
+description: >
+  Runs the structured 9-step feature implementation workflow for Signalist.
+  Trigger this whenever the user asks to add, build, implement, or create any
+  new functionality — a new API endpoint, a new page, a new component, a new
+  domain handler, a new integration, or any new capability that doesn't exist
+  yet. Trigger even if the user doesn't say "feature" explicitly: phrases like
+  "I want to add...", "can you build...", "let's implement...", "we need a..."
+  are all strong signals. Use this skill proactively — it's the right workflow
+  for anything that involves writing new code from scratch.
+---
+
 Read `.claude/workflows/new-feature.md` and start the new feature workflow for: $ARGUMENTS

.claude/commands/quality.md

@@ -1,3 +1,16 @@
+---
+name: quality
+description: >
+  Runs the full quality check suite (lint, static analysis, rector, unit tests)
+  and reports results for Signalist.
+  Trigger this whenever the user wants to verify code quality before committing
+  or opening a PR, after finishing an implementation, when CI is failing, or
+  when they ask about linting, PHPStan errors, test results, or code style.
+  Signals: "run quality", "check the code", "does it pass?", "run the tests",
+  "any lint errors?", "is it ready to commit?", "make quality". Use this skill
+  proactively after any implementation session to catch issues early.
+---
+
 Run the full quality check suite and report results.
 
 Execute in order:

.claude/commands/review.md

@@ -1,3 +1,16 @@
+---
+name: review
+description: >
+  Performs a structured code review of current changes against Signalist's
+  architecture, quality, security, and testing standards.
+  Trigger this whenever the user wants feedback on code they've written or
+  that was just implemented — before opening a PR, after finishing a feature,
+  when they ask "does this look right?", "is this correct?", "can you review
+  this?", or "check my changes". Also trigger when the user explicitly says
+  "review" or asks whether the code follows the project's conventions.
+  Use this skill proactively at the end of any feature or fix session.
+---
+
 Perform a code review of the current changes. Context: $ARGUMENTS
 
 If no context is given, run `git diff HEAD` and `git diff --staged` to get changes.

.claude/commands/simplify.md

@@ -1 +1,17 @@
-Review the recently changed code for clarity, consistency, and maintainability, then fix any issues found. Focus on: removing duplication, improving readability, applying project conventions from `.claude/CLAUDE.md`. Do not change behavior or add features.
+---
+name: simplify
+description: >
+  Reviews recently changed code for clarity, consistency, and maintainability,
+  then fixes any issues found — without changing behavior or adding features.
+  Trigger this when the user wants to clean up, tighten, or polish code that
+  was just written or modified. Signals: "simplify", "clean this up", "refactor
+  this", "make it cleaner", "too complex", "can we improve this?", or after a
+  feature is done and the user wants a final pass before committing. Focus on
+  removing duplication, improving readability, and applying project conventions
+  from CLAUDE.md. Do NOT change behavior or add features.
+---
+
+Review the recently changed code for clarity, consistency, and maintainability,
+then fix any issues found. Focus on: removing duplication, improving readability,
+applying project conventions from `CLAUDE.md`. Do not change behavior or add
+features.