fix(docs): sync command names with install script

[alirezarezvani]

Problem

Fixes #54

The install script builds command names as {category}-{name}:

local dest_dir="$commands_dest/${category}-${cmd_name}"

So commands/development/scaffold installs as development-scaffold, not scaffold.

GETTING-STARTED.md referenced all commands by their short names, causing confusion for users who couldn't find the commands after installing.

Changes

Updated all 33 command references in GETTING-STARTED.md:

Old	Correct
/scaffold	/development-scaffold
/review	/workflow-review
/test-gen	/testing-test-gen
/docs-gen	/documentation-docs-gen

Testing

Verified against scripts/install.sh — the naming pattern ${category}-${cmd_name} is consistent across all command installations.

---

[github-actions]

⛔ Branch Protection Violation

Error: Direct PRs to main are only allowed from dev branch.

Current: fix/issue-54-command-names → main ❌
Required: dev → main ✅

Git Flow Strategy

Our repository follows Git Flow branching strategy:

main (production releases)
  └─ dev (integration branch)
      ├─ feat/* → dev ✅
      ├─ fix/*  → dev ✅
      ├─ docs/* → dev ✅
      └─ ... → dev ✅

How to Fix

1. Close this PR
2. Create PR to dev instead:

   gh pr create --base dev --title "fix(docs): sync command names with install script"

3. After merging to dev, create release PR:

   gh pr create --base main --head dev --title "chore: release vX.Y.Z"

Documentation

• Branching Strategy
• Quick Reference

---

🤖 This check is automated and cannot be bypassed. Please follow the correct workflow.

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.