ingenious: Command for Claude Code

Pull Request Creation

Arguments

• $ARGUMENTS - Base branch for the PR (default: to-stable)

Instructions

Use GitHub CLI to create a pull request targeting the base branch specified in $ARGUMENTS. If no argument is provided, use to-stable as the default base branch.

Pre-PR Analysis

Before creating the PR, perform comprehensive change analysis:

1. Review all commits: Run git log origin/main..HEAD --oneline to see all commits in the PR
2. Review all file changes: Run git diff origin/main..HEAD --stat to see changed files
3. Review detailed changes: Run git diff origin/main..HEAD to see all code changes
4. Categorize changes: Group changes by type (features, bug fixes, refactoring, docs, tests, config)
5. Identify impact: Note which components/modules are affected

PR Guidelines

CRITICAL Requirements:

• NEVER include emojis in PR titles or descriptions
• Maintain a concise, professional tone in all PR content
• DO NOT add attribution footers (e.g., no "Generated with Claude Code")
• DO NOT use squash merge - preserve all commits
• Use clear, descriptive PR titles in imperative mood
• Account for ALL changes - every modified file must be explained in PR description
• Structure PR description with clear sections:
  • Summary: Brief overview of changes
  • Changes: Detailed list of modifications by category
  • Files Modified: List all changed files with brief description
  • Impact: Note any breaking changes or migration steps

Command Format

gh pr create --base <base-branch> --title "Your PR title" --body "Your PR description"

Where <base-branch> is the value from $ARGUMENTS or to-stable if not specified.

Examples

# Using default base branch (to-stable)
gh pr create --base to-stable --title "Add authentication middleware" --body "Add JWT authentication middleware for API endpoints."

# Using custom base branch (e.g., main)
gh pr create --base main --title "Add authentication middleware" --body "Add JWT authentication middleware for API endpoints."