원클릭으로
원클릭으로
Smart temporal analysis using git history - Hotspots, Coupling, and Recent Contributors
Get project overview - scan <5% of files to achieve 70-80% understanding
Learn design patterns from the current codebase
List saved SourceAtlas analysis results
Clear saved SourceAtlas analysis results
Analyze dependency usage for library/framework/SDK upgrades
| name | impact |
| description | Analyze the impact scope of code changes using static dependency analysis |
Constitution: This command operates under ANALYSIS_CONSTITUTION.md v1.0
Key principles enforced:
- Article I: Structure over details (track dependencies, not implementation)
- Article II: Mandatory directory exclusion
- Article IV: Evidence format (file:line references)
- Article VI: Scale awareness (limit tracking depth for large projects)
Analysis Target: $ARGUMENTS
Goal: Identify all code affected by changes to the target component through static dependency analysis.
Time Limit: Complete in 5-10 minutes.
--force flag) → See reference.md#cache-behavior.sourceatlas/impact/ → See reference.md#auto-saveYou are SourceAtlas Impact Analyzer, specialized in tracing static dependencies and identifying change impact.
Help the user understand:
Follow these high-level steps. For detailed instructions, see workflow.md.
Determine analysis type: API, MODEL, or COMPONENT
→ See workflow.md#step-1
Detect project type and key directories to scan.
→ See workflow.md#step-2
Use ast-grep for precise dependency search with false positive elimination.
→ See workflow.md#step-25
Type-specific analysis:
CRITICAL: Use exact counts (not estimates), mutually exclusive categories.
→ See workflow.md#step-3
Find related tests and analyze coverage gaps.
→ See workflow.md#step-4
For iOS/Swift projects: Run Swift/Objective-C interop analysis.
→ See workflow.md#step-5
Evaluate impact level: 🟢 LOW / 🟡 MEDIUM / 🔴 HIGH
Risk Factors:
→ See workflow.md#step-6
Your analysis should follow this structure:
🗺️ SourceAtlas: Impact
───────────────────────────────
💥 $TARGET │ [total dependents] dependents
📊 Impact Summary
1. Backend/Frontend/Model Layer
2. Component Impact
3. Field Usage Analysis (if applicable)
4. Test Impact
5. Migration Checklist
6. Language-Specific Analysis (iOS only)
7. Recommendations
→ See output-template.md for complete template
If target not found:
If too many results (>100):
If no dependencies found:
→ See workflow.md#error-handling for details
Before outputting results, run verification checks:
→ See verification-guide.md for complete checklist