Fix an issue with defined boundaries to prevent unintended changes
Fixes issues with defined boundaries to prevent unintended changes and regressions.
/plugin marketplace add ialameh/sift-coder/plugin install ialameh-siftcoder@ialameh/sift-coder<issue-description>$ARGUMENTS
If no investigation exists, first invoke siftcoder-investigator to:
Define the scope of this fix:
┌─────────────────────────────────────────────────┐
│ MODIFIABLE FILES: │
│ (Only these can be modified) │
│ │
│ [Files will be listed here from investigation] │
│ │
│ PROTECTED FILES: │
│ (Cannot be modified - enforced by hooks) │
│ │
│ Everything else 🔒 │
└─────────────────────────────────────────────────┘
fix/{issue-slug}Invoke siftcoder-coder agent with boundaries:
Invoke siftcoder-qa-reviewer to:
Use these commands to adjust scope:
/siftcoder:scope show - View current boundaries/siftcoder:scope add <file> - Add file to modifiable list/siftcoder:scope remove <file> - Remove file from scope/siftcoder:scope suggest - AI suggests appropriate scopeThe PreToolUse hook will automatically:
After fix, we verify:
Use /siftcoder:blast-radius to re-run this check.
SAFETY FIRST
Ran /investigate first?
→ Great! The boundaries are already set up
→ If not, I'll run it automatically
Want to expand scope?
→ /siftcoder:scope add src/another-file.ts
→ You control what can be modified
Worried about breaking something?
→ Protected files CANNOT be changed
→ /siftcoder:blast-radius verifies nothing broke
Made a mistake?
→ /siftcoder:rollback restores previous state
→ Git checkpoints are created automatically
BEST PRACTICE WORKFLOW:
1. /siftcoder:investigate "issue" ← Explore safely
2. Review the findings
3. /siftcoder:fix "issue" ← Fix with boundaries
4. /siftcoder:blast-radius ← Verify containment
Related commands:
→ /siftcoder:scope show - Current modifiable files
→ /siftcoder:rollback - Undo changes
→ /siftcoder:status - Check fix progress
First, checking for existing investigation or starting one...