ada-commit-impact-analysis

Analyzes commit, branch, and PR diffs to trace change impact across integration points.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/wubing7755/Ada --skill ada-commit-impact-analysis-wubing7755
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ada-commit-impact-analysis
Source: https://github.com/wubing7755/Ada/tree/main/skills/software-development/ada-commit-impact-analysis
Command: npx skills add https://github.com/wubing7755/Ada --skill ada-commit-impact-analysis-wubing7755

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Commit messages rarely tell the whole story of what a change actually does. This Skill reads the full diff of every commit on a branch or PR, traces each change to its real integration points across layers, and verifies claimed behavior with executable evidence so you know the true blast radius before merging. ## Core Features & Use Cases - Full-Diff Commit Review: Enumerates commits against the real baseline, reads every diff hunk, and identifies which invariants, callers, and behaviors changed. - Cross-Cutting Impact Tracing: Greps every consumer of changed types, protocol kinds, and CSS hooks to catch half-dead features that are emitted but unmapped or mapped but unstyled. - Evidence-Based Verification: Runs the project's real gates (typecheck, JS tests, dotnet build/test) and answers questions like "does X still exist?" by tracing the full stack from model to render to CSS to layout, citing file:line evidence. - Use Case: Before merging a PR that adds a new drag-and-drop target kind, use this Skill to confirm the schema, producer, consumer host, presentation CSS, tests, and contract docs were all updated, and to get real test pass counts instead of trusting the commit message. ## Quick Start Ask the agent to read this branch's commits, analyze what changed and what the impact is, and verify the claims by running the project's test gates.

Frequently Asked Questions about ada-commit-impact-analysis

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

FAQPage Schema
How do I analyze what a git branch or PR actually changed?

Enumerate commits against the real baseline with git log origin/main..HEAD, then read the full diff of each commit with git show rather than trusting messages. Trace each touched concept to all its consumers and run the project's test gates to confirm impact.

How to review a pull request's impact before merging?

Read every commit's diff, grep for all consumers of changed types or protocol kinds, and check each layer: schema, producer, consumer host, presentation CSS, tests, and contract docs. A missing slice means the feature is half-dead even if the diff looks complete.

Why shouldn't I trust commit messages during code review?

Commit messages are claims, not code facts. A message may say a fix re-expands a collapsed group, but the planner code may never force that state. Verify every claimed behavior exists in the actual implementation before repeating it.

How do I check if a collapsed or removed UI element still exists in code?

Trace the full stack from model to component render to CSS to layout math instead of reading the diff alone. A collapsed node often survives with visibility hidden and a 0px track, which is different from structural deletion that removes the node and its topology.

When should I not use commit impact analysis?

Do not use it for preparing your own code for review, full code-quality audits, docs-versus-source drift audits, or security reviews. Those tasks belong to dedicated review, quality, audit, and security skills with different verification scopes.