start

Cross-runtime: follow runtime compatibility for invocation, delegation, configuration precedence, state paths, and permissions.

You are helping create a new pull request. Your task is to create a properly named feature branch, optionally fetch ticket details, and store context for subsequent commands.

Step 1: Load Configuration

Resolve project configuration with canonical-first precedence:

if [ -f ".git-workflow/config.yaml" ]; then
  CONFIG_PATH=".git-workflow/config.yaml"
elif [ -f ".claude/config.yaml" ]; then
  CONFIG_PATH=".claude/config.yaml" # legacy read-only fallback
else
  CONFIG_PATH=""
fi

Configuration Priority:

1. .git-workflow/config.yaml (if exists)
2. .claude/config.yaml (legacy read-only fallback)
3. Auto-detection (package.json, pyproject.toml, etc.)
4. Sensible defaults

Default Values (when no config):

workflow:
  type: staging
  developmentBranch: staging
  productionBranch: main
branches:
  feature: "{type}/{ticket}-{description}"
commits:
  types: [Feature, Fix, Hotfix, Refactor, Docs, Test, Chore]
  requireTicket: false
  ticketPattern: "^[A-Z]+-\\d+$"
issueTracker:
  type: auto

Step 2: Gather Information

Ask the user for the following information (use the active host user-input mechanism):

Question 1: Ticket ID

Question: "What is the ticket ID or URL?"

• Examples:
  • PROJ-1234 (Jira format)
  • ENG-456 (Linear format)
  • #789 (GitHub issue)
  • https://linear.app/team/issue/ENG-456/...
  • https://your-org.atlassian.net/browse/PROJ-1234

Parsing Logic:

• Extract ticket ID from URL if provided
• Linear: Pattern /issue/([A-Z]+-\d+)/
• Jira: Pattern /browse/([A-Z]+-\d+)
• GitHub: Pattern issues/(\d+) or #(\d+)

Validation:

• If commits.requireTicket: true in config, ticket is required
• Validate against commits.ticketPattern if provided
• If no ticket provided and not required, proceed without it

Question 2: Change Type