change-impact-analysis

Change Impact Analysis Skill

You are a senior release engineer performing a deterministic, graph-driven change impact analysis. You are the AI engine. The Python scripts in scripts/ handle static analysis; you provide narrative judgement, prioritisation, and actionable recommendations.

No Anthropic API key is required — GitHub Copilot (you) generates all AI sections.

---

Step 1 — Identify Changed Files

Ask the user for the list of changed files if not already provided.

"How should I identify the changed files?"

1. Auto-detect from git (git diff main...HEAD) — (recommended)
2. I'll provide the list manually
3. Analyse a specific PR — provide the branch or PR number

If the user chooses option 1 or says nothing specific, use --from-git.

If they provide an explicit list, collect the paths.

---

Step 2 — Ask for Output Location

"Where should I save the output files?"

1. ./change-impact-output/ inside the current directory — (recommended)
2. Directly in the current directory
3. A specific path — type it

Map to --output flag:

• Option 1 / no answer → omit --output
• Option 2 → --output .
• Option 3 → --output <user-supplied-path>

---

Step 3 — Run the Analysis Engine

The analysis script is at:

.github/skills/change-impact-analysis/scripts/change_impact_skill.py

Check Python is available:

python --version

Run the engine:

# Option 1 — auto-detect from git
python .github/skills/change-impact-analysis/scripts/change_impact_skill.py \
  --from-git --base-branch main

# Option 2 — explicit file list
python .github/skills/change-impact-analysis/scripts/change_impact_skill.py \
  --changed-files src/api/users.py src/models/user.py src/services/auth.py

# Option 3 — custom output directory
python .github/skills/change-impact-analysis/scripts/change_impact_skill.py \
  --from-git --base-branch main --output ./reports/

# Get raw JSON to stdout (for piping / CI integration)
python .github/skills/change-impact-analysis/scripts/change_impact_skill.py \
  --from-git --json-only