hf.check-cross-service-impact

Cross-service impact detection flags edits to Python files under shared/ by identifying imports from shared and warning you with a list of affected services before changes are merged.

To reduce warning fatigue, shared code edit warnings trigger only once per 4-hour session by writing a marker to /tmp, ensuring developers are alerted without repeated interruptions.

Yes, the pretool hook inspects edited file paths and restricts checks to Python files under shared/, explicitly excluding tests to focus warnings on actual downstream service impacts.

A pretool hook intercepts edits to shared Python files, detects downstream imports from shared, and warns once per session with affected services and guided remediation steps.

No, this shared code impact warning tool operates as a standalone pretool hook with no external dependencies, using only local /tmp markers to manage session-based noise reduction.

When editing shared code affects other services, the warning suggests targeted tests and review steps for the affected services to guide safe remediation before merging changes.