Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

hyp impact_en.md

maoxiaoyue edited this page May 14, 2026 · 1 revision

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

HypGo

繁體中文 | English


中文文件

設計文件

套件

AI 協作工具鏈

CLI 命令


English Docs

Design Docs

Packages

AI Collaboration Toolchain

CLI Commands

Clone this wiki locally

AltStyle によって変換されたページ (->オリジナル) /