hyp impact_en.md

hyp impact — Change Impact Analysis

Analyze what packages, routes, and tests would be affected by modifying a Go file. Run before modifying shared packages.

Usage

hyp impact <file.go>

Example

hyp impact pkg/errors/catalog.go

Output:

Impact Analysis: pkg/errors/catalog.go
Package: pkg/errors

Direct dependents (import this package):
  → pkg/contract
  → pkg/diagnostic
  → pkg/scaffold

Affected tests:
  → pkg/errors/*_test.go (19 tests)
  → pkg/contract/*_test.go (24 tests)
  Total: 43 tests

Risk: MEDIUM (3 packages depend on this)

Risk Levels

Level	Condition
LOW	< 2 dependent packages, < 20 tests
MEDIUM	2-4 dependent packages or 20-49 tests
HIGH	>= 5 dependent packages or >= 50 tests

Recommendations

Risk	Action
LOW	Modify directly, run affected tests
MEDIUM	Run all dependent package tests after modification
HIGH	Discuss with team before modifying

Safety

• Read-only analysis, never modifies files
• Only scans import paths, never reads function bodies
• Path validated within project directory

Related Commands

• hyp chkcomment — Check comments after modifying