What problem does it solve? Cross-layer changes in the Guardian repository can silently break upstream clients, SDKs, examples, and docs. This Skill turns a proposed change, bug, or diff into a concrete impact report naming the affected files, propagation layers, validation commands, and documentation surfaces before implementation or review. ## Core Features & Use Cases - Change Classification: Categorizes requests into server contract, canonicalization, auth/signature, client parity, multisig lifecycle, browser signer, or deploy/release changes using a structured impact matrix. - Bottom-Up Propagation Analysis: Identifies the lowest affected layer (server, Rust client, TypeScript client, multisig SDKs, examples) and enumerates every upstream surface that must be updated. - Validation Planning: Maps each change class to the minimum cargo tests, npm tests, and manual smoke checks required. - Use Case: Before editing guardian.proto endpoint semantics, run this Skill to discover that server HTTP/gRPC handlers, both client packages, conversion modules, and multisig SDKs all need coordinated updates plus targeted test runs. ## Quick Start Use guardian-change-impact to map my proposed change to the push_delta endpoint across all affected layers and list the required tests and docs updates.
