smith-explore

Pre-change impact analysis reveals cross-system touchpoints by auditing skills, hooks, and cross-references concurrently. It scans the codebase to detect scope, dependencies, and potential conflicts before applying changes, generating a structured report with severity-based findings.

You audit a codebase for policy and configuration conflicts by running a read-only exploration of the proposed changes. This process enforces policy checks and scans configurations to surface risks and redundancies without modifying the actual code.

Yes, you can run a read-only exploration to detect scope and dependencies without modifying code. The analysis operates in a phase-driven, read-only mode that logs findings and generates actionable recommendations while ensuring the codebase remains untouched.

The best way to identify cross-references and redundancies when introducing features is to use concurrent sub-agent analysis. This approach scans skills and hooks to surface potential conflicts, generating an exploration report with actionable recommendations for decision-making.

Yes, the impact analysis enforces policy checks for configuration updates and feature introductions. It scans the codebase to surface risks associated with these changes, logging all findings into a structured exploration report with severity-based conflicts.

A limitation of read-only codebase exploration is that it generates findings and recommendations without modifying code. Users must manually apply the suggested resolutions from the exploration report to resolve severity-based conflicts and cross-system touchpoints.