Stats
Actions
Tags
From harness-claude
Performs graph-based impact analysis on changed files from diff or specified paths/files, querying impact graph to report potential breakages ranked by risk.
How this command is triggered — by the user, by Claude, or both
Slash command
/harness-claude:impact-analysis [--path <path>] [--files <files>]commands/Files this command reads when invoked
This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
<!-- Generated by harness generate-slash-commands. Do not edit. --> <context> Cognitive mode: analytical-reporter Type: rigid </context> <objective> Graph-based impact analysis — answers "if I change X, what breaks?" Phases: - identify: Identify changed files from diff or input - analyze: Query graph for impact of each changed file - assess: Rank findings by risk and generate report </objective> <execution_context> @agents/skills/claude-code/harness-impact-analysis/SKILL.md @agents/skills/claude-code/harness-impact-analysis/skill.yaml </execution_context> <process> 1. Try: invoke mc...
Phases:
<execution_context> @agents/skills/claude-code/harness-impact-analysis/SKILL.md @agents/skills/claude-code/harness-impact-analysis/skill.yaml </execution_context>
1. Try: invoke mcp__harness__run_skill with skill: "harness-impact-analysis" 2. If MCP unavailable: read SKILL.md and follow its workflow directly 3. Pass through any arguments provided by the usernpx claudepluginhub intense-visions/harness-engineering --plugin harness-claude/what-would-breakAnalyzes blast radius of proposed code changes via dependency mapping, risk assessment, and mitigation strategies to teach impact analysis.
/diff-impactAnalyzes git diff changes against a code knowledge graph to show directly touched nodes and their ripple effect (dependents via BFS). Useful before merging PRs to assess blast radius.
/SKILLAnalyzes impact of changes to a target (API/model/component) via static dependency analysis, listing affected code, indirect dependencies, tests, and migration checklist.
/impact-analysisAnalyzes the impact of code changes by identifying affected files and assessing risk. Guides the user through defining the change scope, then produces layered analysis files grouped by layer (core, API, service, etc.) and a final summary.
/impactFans out parallel agents to map the blast radius of a file, function, or directory before making changes — imports, tests, CI pipelines, docs, and code owners.
/vcsdd-coherence-impactRuns BFS forward-impact analysis from changed nodes through the CEG, surfacing CoDD must_review alerts alongside Green/Amber/Gray downstream impact bands.