impact-analysis: PHP コード影響調査スキル

PHP impact analysis tracks how a change propagates across functions, methods, and interfaces in a repository by generating deterministic BFS traces using ripgrep and LSP, resulting in an evidence TSV and a summary report.

To perform PHP impact tracing, you need the impact tool, ripgrep, and a PHP LSP server installed, plus configuration parameters like repository path, output directory, max depth, and max nodes to control the BFS scope.

Yes, PHP impact analysis supports single or multiple starting points with optional implementation resolution for interface methods, allowing you to map change propagation comprehensively across your PHP repository.

Analyzing PHP code impact generates an evidence.tsv file for machine processing and a summary.md file for human review, both documenting how changes propagate across functions, methods, and interfaces.

You control the BFS trace scope by setting configuration parameters like repository path, output directory, max depth, and max nodes, which limit the breadth and depth of the PHP impact analysis.