[Bug] Git-Manager Agent provides incomplete workflow when pre-commit hooks fail

Resolved 💬 5 comments Opened Sep 16, 2025 by BucklerCTO Closed Jan 5, 2026

[Bug] Git-Manager Agent provides incomplete workflow when pre-commit hooks fail

Bug Description

Git-manager agent runs pre-commit hooks but doesn't complete the commit workflow when hooks fail, leaving users with staged but uncommitted files without clear explanation.

Expected Behavior

  • Agent should detect pre-commit hook failures clearly
  • Agent should report the failure with actionable information
  • Agent should offer alternatives (--no-verify, fix tests, disable hooks, etc.)
  • Agent should complete the git workflow or provide clear status about why it was blocked

Actual Behavior

  • Agent runs pre-commit hooks which fail on test runner
  • Agent doesn't clearly communicate that commit was blocked by hook failure
  • User is left with staged but uncommitted files without clear explanation
  • No actionable guidance provided for resolving the blocking issue

Reproduction Steps

  1. Have failing integration tests in the codebase that will cause pre-commit hooks to fail
  2. Use git-manager agent to "commit all files and push"
  3. Pre-commit hooks fail on smart test runner
  4. Agent doesn't complete workflow or provide clear status about the blockage

Impact

  • Confusing user experience - files appear uncommitted without clear reason
  • Incomplete git workflow execution
  • User has to manually diagnose why files remain uncommitted
  • Breaks the promise of "commit and push all files" functionality
  • No guidance on how to resolve the blocking issue

System Information

  • Platform: macOS (Darwin 24.3.0)
  • Claude Code: Latest version with git-manager agent
  • Repository: Git repo with pre-commit hooks configured
  • Hook failure: Smart test runner failing on integration tests

Current Agent Output

Agent shows pre-commit hook execution but doesn't clearly state:

  1. That the commit was blocked due to hook failure
  2. What specific test failures caused the block
  3. What options are available to proceed (--no-verify, fix tests, etc.)

Expected Fix

  • Enhanced error handling for pre-commit hook failures
  • Clear status messages about commit blocking with specific failure reasons
  • Actionable alternatives when commits are blocked (offer --no-verify option)
  • Complete the promised workflow or clearly explain why it cannot be completed
  • Better integration between git operations and test failure reporting

Suggested Improvements

  1. Clear Failure Communication: "Commit blocked by failing pre-commit hooks"
  2. Specific Failure Details: Report which hook failed and why
  3. Actionable Options: Offer to retry with --no-verify or fix failing tests
  4. Status Clarity: Make it obvious when files remain staged but uncommitted

Labels

  • bug
  • has repro
  • platform:macos
  • area:core
  • git-manager
  • pre-commit

View original on GitHub ↗

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