Use --force in /mob-remove for non-current mobs#33
Merged
Conversation
The slash command was calling `codemob remove <name>` which triggers an interactive y/N confirmation prompt that agents can't handle cleanly. Now the slash command gets confirmation from the user first, warns about destructive consequences (unstaged/uncommitted/unpushed changes), then calls `codemob remove --force <name>` to skip the redundant CLI prompt. Closes #32
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/mob-removeslash command now warns the user about destructive consequences (unstaged/uncommitted/unpushed changes will be lost) when removing a non-current mobcodemob remove --force <name>to bypass the interactive y/N prompt that agents can't handle cleanly--forceflag already existed in the CLI - the slash command just wasn't using itCloses #32
Test plan
/mob-remove, pick a non-current mob, verify the agent warns about data loss before proceeding--forceand doesn't get stuck on the interactive prompt