/ripple

Ripple Analysis Template

Combined analysis report including both vertical impact and horizontal consistency checks.

Usage

Use this template (default) for comprehensive change analysis:

• "Analyze the impact of this change"
• "What should I know before implementing?"
• "Is this change safe to proceed?"

Template

# Ripple Analysis Report

## Executive Summary

**Change:** [Brief description of the proposed change]
**Requested By:** [Source - user request, Nexus chain, Scout investigation, etc.]
**Analysis Date:** YYYY-MM-DD

### Quick Assessment

| Metric | Value | Status |
|--------|-------|--------|
| **Risk Score** | X.X / 10 | 🟢 LOW / 🟡 MEDIUM / 🟠 HIGH / 🔴 CRITICAL |
| **Direct Impact** | X files | |
| **Transitive Impact** | Y files | |
| **Breaking Changes** | N | |
| **Pattern Violations** | M | |
| **Test Coverage** | P% | 🟢 Good / 🟡 Moderate / 🔴 Poor |

### Recommendation

**Verdict:** ✅ GO / ⚠️ CONDITIONAL GO / 🛑 NO-GO

**Rationale:** [1-2 sentences explaining the recommendation]

**Conditions (if CONDITIONAL GO):**
- [ ] [Condition 1]
- [ ] [Condition 2]

---

## 1. Change Scope

### What is Being Changed

| Aspect | Description |
|--------|-------------|
| **Target File(s)** | `src/path/to/file.ts` |
| **Change Type** | [New Feature / Modification / Refactoring / Deletion / Rename] |
| **Change Description** | [Detailed description] |

### Proposed Modification

```typescript
// Current State
[existing code or "N/A for new files"]

// Proposed State
[proposed code or description]

Key Changes

1. [Change 1]: [Description]
2. [Change 2]: [Description]
3. [Change 3]: [Description]

2. Vertical Impact Analysis

Dependency Overview

[Changed File]
       │
       ├──► [Direct 1] ──► [Trans 1.1]
       │
       ├──► [Direct 2] ──► [Trans 2.1]
       │                    └──► [Trans 2.2]
       │
       └──► [Direct 3]

Affected Files Summary

Direct Dependents (Level 1)

Breaking Changes

Breaking Change Details:

Breaking Change 1: functionA

• Current: functionA(param: string): Result
• Proposed: functionA(param: string, options?: Options): Result
• Impact: All callers need review
• Migration: Non-breaking (new param is optional)

Breaking Change 2: TypeB

• Current: { oldProp: string }
• Proposed: { newProp: string }
• Impact: All type usages break
• Migration: Find-replace required

Cascade Risks

3. Horizontal Consistency Analysis

Pattern Compliance Overview

Naming Convention Check

Pattern Compliance

Established Patterns

1. Error Handling

• Codebase Pattern: Try-catch with custom error class
• Proposed: ✅ Follows pattern
• Reference: src/services/baseService.ts

2. Data Fetching

• Codebase Pattern: React Query with standardized options
• Proposed: ✅ Follows pattern
• Reference: src/hooks/useUser.ts

3. State Management

• Codebase Pattern: Zustand with typed slices
• Proposed: ✅ Follows pattern
• Reference: src/store/userStore.ts

Style Violations

Similar Files for Reference

4. Risk Assessment Matrix

Risk Dimensions

Calculation

Risk Score = (X×0.30) + (Y×0.25) + (Z×0.20) + (W×0.15) + (V×0.10)
           = [calculation]
           = X.X / 10

Risk Level

This Change: [X.X] - [LEVEL]

5. Test Coverage Analysis

Affected Code Coverage

Tests Requiring Updates

Suggested New Tests

6. Recommendations

Action Items

Before Implementation

• Review breaking change migration paths
• Add tests for uncovered dependent code (via Radar)
• Confirm pattern compliance for [specific area]

During Implementation

• Follow patterns in src/reference/similar.ts
• Update all direct dependents
• Maintain backward compatibility where marked

After Implementation

• Run full test suite
• Verify type checking passes
• Update affected documentation

Suggested Implementation Order

1. Phase 1: Update type definitions
2. Phase 2: Update core implementation
3. Phase 3: Update direct dependents
4. Phase 4: Run tests and verify
5. Phase 5: Update documentation

Risk Mitigations

7. Next Steps

Recommended Agent Chain

Handoff Information

For Builder:

• Direct files to modify: [list]
• Patterns to follow: [references]
• Breaking changes to handle: [list]
• Tests to update: [list]

For Guardian:

• Suggested PR scope: [description]
• Logical groupings: [groups]
• Breaking change notes: [for changelog]

Appendix: Commands Used

# Dependency analysis
grep -rl "from.*target-module" src --include="*.ts"
npx madge --depends-on src/target.ts src/

# Pattern analysis
grep -E "pattern" src/**/*.ts
find src -name "*.ts" -exec grep -l "pattern" {} \;

# Coverage check
npx jest --coverage --collectCoverageFrom="src/target.ts"

## Quick Reference Checklist

### Completeness

- [ ] Executive summary with clear verdict
- [ ] Change scope clearly defined
- [ ] All direct dependents identified
- [ ] Transitive dependencies traced
- [ ] Breaking changes documented
- [ ] Pattern compliance checked
- [ ] Risk score calculated with evidence
- [ ] Test coverage gaps identified
- [ ] Recommendations are actionable
- [ ] Next steps defined

### Quality Gates

- [ ] Risk score justified with evidence
- [ ] All 5 risk dimensions scored
- [ ] Pattern violations have file:line references
- [ ] Recommendations include specific actions
- [ ] Handoff information is complete