change-explainer

Generates terminal TXT/ANSI or HTML reports explaining git diffs, evidence, and validation results.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/amitkarpe/agent-skills --skill change-explainer-amitkarpe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: change-explainer
Source: https://github.com/amitkarpe/agent-skills/tree/main/skills/change-explainer
Command: npx skills add https://github.com/amitkarpe/agent-skills --skill change-explainer-amitkarpe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires rich, and includes scripts (resource) and references (resource) components.

What problem does it solve? Raw git diffs and scattered validation logs are hard to review, making it difficult to understand why a code or infrastructure change matters, what its blast radius is, and whether it was properly validated. ## Core Features & Use Cases - Terminal Change Reports: Renders 3-5 panel TXT/ANSI summaries covering why the change matters, what changed, evidence, validation ledger, and risk/gate footer using Python Rich. - Optional HTML Cockpit: Publishes a dark-themed HTML change dashboard to a local web path with URL validation when browser output is explicitly requested. - Validation Detection: Scans evidence files for known validation patterns (auth, cleanup, secrets, PROD boundary, syntax checks) and marks each as PASS or CHECK. - Use Case: After finishing a Terraform or script change, run the explainer to produce a single .ansi file showing the before/after delta, touched files, evidence paths, and PROD gate status for review. ## Quick Start Ask the agent to show a change explainer for the current repo diff, including the goal, why it matters, and any evidence directories from the task.

Frequently Asked Questions about change-explainer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a summary of my git diff changes?▼

Run the change_explainer.py script in txt mode against your repo to render a Rich-based terminal report covering why the change matters, files changed, evidence, and validation. The output is saved as both .txt and .ansi evidence files, with the .ansi copy also placed at /tmp/change.ansi.

How do I create an HTML report of code changes?▼

Use the html or both mode of the script to publish a dark-themed HTML cockpit to /opt/crypto-web/demos/<slug>/index.html. The script validates the resulting local URL with curl before reporting success, and HTML is only generated when explicitly requested.

Does the change report require the Rich Python library?▼

Rich is the default renderer for colored ANSI panels, but it is optional. If Rich is not installed, the script falls back to plain TXT output, so the core explainer works with standard Python plus git only.

What validation checks does the change explainer detect?▼

It scans the goal, why text, and evidence files for patterns covering FQDN paths, app authentication, CRUD cleanup, secret printing, DNS/Route53, PROD boundary, script syntax, and repo checks. Each check is marked PASS or CHECK in the validation ledger.

When should I use detail mode for change reports?▼

Use the --detail flag only for complex changes needing the causal spine, full delta tables, AWS resource facts, goal execution, and task improvement panels. Default output stays at 3-5 concise panels to keep reviews focused.