[BUG] /git:commit-push-pr command does not follow commands (AI generated) with Claude Haiku model

Resolved 💬 4 comments Opened Jan 2, 2026 by generik0 Closed Jan 6, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

The /git:commit-push-pr command i have made does not work correctly when using Claude Haiku (claude-haiku-4-5-20251001) model. The skill appears to either not execute properly or doesn't follow the documented workflow.

it should have, and the sonnet + opus models work:

  1. Execute /git:commit-push to commit and push changes
  2. Read the PR template from .github/pull_request_template.md
  3. Extract branch name and determine PR type
  4. Create a pull request using gh pr create with proper formatting

The commands ensure the useaf of a PR template and holistic chunking of commits

What Should Happen?

  1. Execute /git:commit-push to commit and push changes
  2. Read the PR template from .github/pull_request_template.md
  3. Extract branch name and determine PR type
  4. Create a pull request using gh pr create with proper formatting

Error Messages/Logs

⏺ Now let me create the PR:

⏺ Bash(gh pr create \
        --title "Maintenance | BNKI-620 | Fix SMOOTH workflow orchestration and FRIGG validation" \…)
  ⎿  https://github.com/0north/bunker-procurement/pull/4262

Steps to Reproduce

  1. Set model to Claude Haiku: /model → select Haiku
  2. On a git branch with commits ready to push
  3. Run /git:commit-push-pr
  4. Observe that the skill doesn't execute the proper workflow

Claude Model

Other

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.0.76

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

IntelliJ IDEA terminal

Additional Information

commands:

commit-push.md
commit.md
commit-push-pr.md

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗