Skip to content

fix(debug-loop): add Plan Mode rejection/revision loop #191

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
maystudios merged 1 commit into from
Mar 25, 2026
Merged

fix(debug-loop): add Plan Mode rejection/revision loop #191

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions templates/commands/maxsim/debug-loop.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,8 +33,12 @@ Invoke the `autoresearch` skill (debug workflow) to drive the investigation loop
- **Scope** — which files/directories are likely involved (or "unknown")
3. Attempt initial reproduction — run the reproduction command to confirm the bug exists
4. Create a GitHub Issue labeled `debug` to track the session
5. Show the investigation plan and confirm with user
6. Exit Plan Mode via ExitPlanMode
5. Show the investigation plan and ask user to confirm
6. **Handle user response:**
- **If user approves:** proceed to step 7
- **If user requests changes:** revise the relevant parameters (scope, reproduction command, investigation approach). If the reproduction command changed, re-attempt reproduction (step 3). Update the GitHub Issue body with the revised plan. Return to step 5 (stay in Plan Mode).
- **If user cancels:** close the GitHub Issue created in step 4 (`gh issue close {ISSUE_NUM} --comment "Debug session cancelled by user before investigation began"`), Exit Plan Mode via ExitPlanMode, and stop.
Comment on lines +39 to +40
Copy link

Copilot AI Mar 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Step 6’s cancel path references {ISSUE_NUM}, but this template otherwise uses $... variables (e.g., $ARGUMENTS) and doesn’t define/capture an issue number in step 4. This makes the cancellation instruction ambiguous/unenforceable. Consider explicitly capturing the created issue number/URL in step 4 and then referencing it consistently here (e.g., $ISSUE_NUM, consistent with templates/workflows/debug.md).

Copilot uses AI. Check for mistakes.
7. Exit Plan Mode via ExitPlanMode

**Phase 2 — Debug Loop**

Expand Down
Loading