Test debug command enhancements and fix protected branch workflow #109

New Issue

lmiranda · 2026-01-22T23:07:14Z

lmiranda commented

2026-01-22 23:07:14 +00:00

Context

PR #107 added enhancements to /debug-report and /debug-review commands:

Sprint context detection
Smart labeling via suggest_labels
Lessons learned search and capture
Non-blocking hooks

Tasks

1. Test Debug Command Enhancements

Test /debug-report on a project with active sprint - verify sprint association prompt appears
Test /debug-report on development branch - verify no prompt (standalone fix mode)
Test /debug-review - verify lessons learned search before fix proposal
Test lesson capture at issue closure (Step 15)
Verify hooks no longer block workflow on doc/config edits

2. Fix Protected Branch Workflow

When committing to development, Claude attempted direct push and got:

remote: error: Not allowed to push to protected branch development
! [remote rejected] development -> development (pre-receive hook declined)
error: failed to push some refs

Problem: Claude committed to development first, then had to create a feature branch and reset.

Solution Implemented:

Updated /commit command to detect protected branches BEFORE committing
Warns user when on a protected branch
Offers to create a feature branch automatically
Uses configurable GIT_PROTECTED_BRANCHES environment variable

Acceptance Criteria

Debug commands work as documented
git-flow handles protected branches gracefully

## Context PR #107 added enhancements to `/debug-report` and `/debug-review` commands: - Sprint context detection - Smart labeling via `suggest_labels` - Lessons learned search and capture - Non-blocking hooks ## Tasks ### 1. Test Debug Command Enhancements - [x] Test `/debug-report` on a project with active sprint - verify sprint association prompt appears - [x] Test `/debug-report` on `development` branch - verify no prompt (standalone fix mode) - [x] Test `/debug-review` - verify lessons learned search before fix proposal - [x] Test lesson capture at issue closure (Step 15) - [x] Verify hooks no longer block workflow on doc/config edits ### 2. Fix Protected Branch Workflow When committing to `development`, Claude attempted direct push and got: ``` remote: error: Not allowed to push to protected branch development ! [remote rejected] development -> development (pre-receive hook declined) error: failed to push some refs ``` **Problem:** Claude committed to `development` first, then had to create a feature branch and reset. **Solution Implemented:** - Updated `/commit` command to detect protected branches BEFORE committing - Warns user when on a protected branch - Offers to create a feature branch automatically - Uses configurable `GIT_PROTECTED_BRANCHES` environment variable ## Acceptance Criteria - [x] Debug commands work as documented - [x] git-flow handles protected branches gracefully

lmiranda closed this issue

2026-01-23 15:48:15 +00:00

lmiranda reopened this issue

2026-01-23 15:54:13 +00:00

lmiranda referenced this issue from a commit

2026-01-23 16:05:20 +00:00

fix: protected branch detection and non-blocking hooks

lmiranda referenced a pull request that will close this issue

2026-01-23 16:06:01 +00:00

fix: protected branch detection and non-blocking hooks #111

lmiranda referenced this issue from a commit

2026-01-23 16:08:07 +00:00