Slash Commands Reference

Complete reference for all available slash commands. These custom Claude Code commands automate common development workflows.

Development Workflow

/pr-create

Create a pull request with comprehensive description and automated quality gates.

Usage:

/pr-create

What It Does:

1. Checks if branch needs rebasing onto master
2. Checks if PHPStan analysis is required (PHP files changed)
3. Fetches issue details from GitHub
4. Creates PR with comprehensive description template
5. Links PR to related GitHub issue

Quality Gates:

• Rebase validation (ensures branch is up-to-date)
• PHPStan analysis (for PHP file changes)

---

/rebase-master

Rebase current branch onto latest master and resolve conflicts.

Usage:

/rebase-master

What It Does:

1. Fetches latest master from origin
2. Rebases current branch onto master
3. Detects conflicts and guides resolution
4. Verifies rebase completed successfully

When to Use:

• Before creating a PR
• After master has advanced significantly
• Before merging your branch

---

/commit

Create a git commit with proper formatting.

Usage:

/commit [optional-message]

# Examples
/commit "Add booking validation"
/commit

Commit Format:

ISSUE-NUMBER Description of changes

Example:
195 Add booking validation service

---

Code Quality

/fix-phpstan

Run PHPStan analysis and automatically fix all detected errors.

Usage:

# Analyze entire application
/fix-phpstan

# Analyze specific file
/fix-phpstan app/Services/BookingService.php

# Analyze directory
/fix-phpstan app/Services

Phases:

1. Phase 1: Runs PHPStan analysis to identify errors
2. Phase 2: Automatically fixes all errors
3. Phase 3: Verifies all errors are resolved
4. Phase 4: Prompts to commit changes

Common Fixes Applied:

• Missing PHPDoc array type annotations
• Using env() outside config files
• Missing return type declarations
• Untyped properties

---

Issue Management

/issue-create

Create a GitHub issue with complexity estimation and detailed description.

Usage:

/issue-create [feature-description]

# Example
/issue-create Add email notifications for booking confirmations

What It Does:

1. Analyzes feature requirements
2. Estimates complexity (Small/Medium/Large)
3. Breaks down into technical tasks
4. Creates GitHub issue with comprehensive description

Complexity Levels:

• Small: 1-4 hours, single file changes
• Medium: 4-16 hours, multiple files
• Large: 16+ hours, architectural changes

---

/issue-work

Start working on an existing GitHub issue by setting up a feature branch.

Usage:

/issue-work ISSUE_NUMBER

# Example
/issue-work 195

What It Does:

1. Fetches issue details from GitHub
2. Creates feature branch with naming convention
3. Checks out the new branch
4. Displays issue context and tasks

Branch Naming:

<issue-number>-<slugified-title>

Example:
195-integrate-larastan-workflow

---

Documentation

/update-docs

Update documentation for recently changed backend services.

Usage:

/update-docs

# Or for specific service
/update-docs BookingService

What It Does:

1. Detects recently modified service files
2. Updates corresponding documentation
3. Verifies code examples are accurate
4. Updates API reference if endpoints changed

---

Quick Reference

Command	Category	Purpose	Required Args
/pr-create	Workflow	Create PR with quality gates	None
/rebase-master	Workflow	Rebase onto latest master	None
/commit	Workflow	Create formatted commit	Optional message
/fix-phpstan	Quality	Run and fix PHPStan errors	Optional path
/issue-create	Issues	Create GitHub issue	Feature description
/issue-work	Issues	Start working on issue	Issue number
/update-docs	Docs	Update service documentation	Optional service

Common Workflows

Starting New Feature

# 1. Create GitHub issue
/issue-create Add customer export functionality

# 2. Start working on the issue
/issue-work 196

# 3. Implement the feature
# ... coding ...

# 4. Fix type safety issues
/fix-phpstan app/Services/CustomerService.php

# 5. Commit changes
/commit "Implement customer export service"

# 6. Update documentation
/update-docs CustomerService

# 7. Create pull request
/pr-create

Fixing a Bug

# 1. Create branch for bug fix
/issue-work 197

# 2. Fix the bug
# ... coding ...

# 3. Run static analysis
/fix-phpstan

# 4. Commit the fix
/commit "Fix booking validation null pointer"

# 5. Create PR
/pr-create

Tips and Best Practices

Command Execution Order

Typical sequence:

1. /issue-work - Set up branch
2. Code your feature
3. /fix-phpstan - Fix type safety
4. /commit - Commit changes
5. /update-docs - Update docs
6. /pr-create - Create PR

Error Recovery

If /pr-create stops you:

# Rebase if needed
/rebase-master

# Fix PHPStan if needed
/fix-phpstan

# Retry PR creation
/pr-create

Efficiency Tips

1. Run PHPStan early and often - Don’t wait until PR time
2. Commit frequently - Use /commit for small, logical changes
3. Update docs as you code - Don’t save for the end
4. Use /rebase-master regularly - Stay current with master

Troubleshooting

Command Not Found

# List available commands
/help

# Check command exists
ls .claude/commands/

Quality Gate Blocks PR

This is expected behavior:

1. Follow the prompted command (/fix-phpstan)
2. Wait for fixes to complete
3. Review and commit fixes
4. Retry /pr-create