noodlbox

Change Planning

Analyze blast radius and verify impact before committing

Analyze uncommitted git changes and understand their ripple effects through the codebase.

Invoke with: /noodlbox:change-planning

Quick Decision

Workflowchange_scopebase_ref
Before staging"unstaged"-
Before commit"staged"-
All uncommitted"all"-
Compare to branch"compare""main"

Tool Reference

noodlbox_detect_impact

Detect which processes are affected by git changes.

noodlbox_detect_impact(
  repository: "current",
  change_scope: "all",
  include_content: false,
  max_processes: 10
)

Parameters:

  • change_scope: What changes to analyze (see table above)
  • base_ref: Branch/commit to compare against (for "compare" scope)
  • include_content: Include symbol source code in response
  • max_processes: Limit results per page

Risk Assessment

MetricLow RiskMedium RiskHigh Risk
changed_symbols_count< 55-15> 15
total_impacted_processes< 1010-30> 30
Cross-community changesNone1-2> 2

Workflow Checklist

Pre-Commit Review

Pre-Commit Checklist:
- [ ] Run impact detection (scope: staged)
- [ ] Check changed_symbols count
- [ ] Review each impacted_process
- [ ] Verify changes are intentional
- [ ] Split commit if impact > 10 processes

Code Review

Code Review Checklist:
- [ ] Run impact detection (scope: compare, base_ref: target_branch)
- [ ] Check cross-community impact
- [ ] Verify test coverage for impacted areas
- [ ] Flag high-centrality changes
- [ ] Document coordination needs

Example: Pre-Commit Check

Task: "What will my changes affect before I commit?"

Run impact detection

"What will my staged changes affect?"

Uses: noodlbox_detect_impact with change_scope: "staged"

Summary: 3 changed symbols, 7 impacted processes

Review changed symbols

  • validatePayment (src/payments/validator.ts:42) - Modified
  • PaymentError (src/payments/errors.ts:15) - Modified
  • formatAmount (src/payments/utils.ts:88) - Modified

Review impacted processes

  • "Checkout flow" (5 steps affected)
  • "Payment retry" (3 steps affected)
  • "Webhook handler" (2 steps affected)

Assess risk

  • Changed: 3 symbols → Low
  • Impacted: 7 processes → Low
  • Cross-community: None → Low
  • Overall: Low risk, safe to commit

Output Format

Low Impact (< 10 processes)

## Impact Summary

- **Changed**: 3 symbols in 2 files
- **Affected**: 7 processes
- **Risk**: Low

## Changed Code

| Symbol | File | Type |
|--------|------|------|
| validatePayment | src/payments/validator.ts:42 | Modified |

## Affected Flows

1. **Checkout flow** - 5 steps include changed symbols
   - Entry: `handleCheckout``processPayment``validatePayment`
   - Risk: Low (isolated change)

## Recommendations

- [ ] Run payment integration tests
- [ ] Verify checkout flow manually

High Impact (> 10 processes)

Delegate to codebase-analyst agent for detailed analysis.

When to Use Something Else

NeedUse Instead
Explore unfamiliar codeExploring Codebases
Generate documentationGenerating Documentation
Debug failing codeDebugging
Plan large refactorsRefactoring

On this page