skills.rest
OrestesK
OrestesKCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

semantic-git

Analyze structural code changes and downstream impact via semantic diffs.

2|Updated May 5, 2026
Search Tags:#code review#code analysis#impact analysis#blast radius#git blame#semantic git#structural diff
One-click install
npx skills add https://github.com/OrestesK/pi --skill semantic-git-orestesk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: semantic-git
Source: https://github.com/OrestesK/pi/tree/main/skills/semantic-git
Command: npx skills add https://github.com/OrestesK/pi --skill semantic-git-orestesk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill replaces line-by-line Git inspection with structural analysis of changed code entities and their dependencies, making it easier to understand meaningful changes and potential blast radius.

Core Features & Use Cases

  • Structural Diffs: Identify changed functions, classes, and other code entities with semantic diff analysis.
  • Impact Analysis: Trace downstream dependencies to determine which parts of a codebase may be affected.
  • Change Investigation: Inspect surrounding context, entity-level blame, history, and file entities when reviewing or debugging changes.
  • Use Case: Before merging a refactor, use the Skill to identify the changed functions and determine which callers and dependent components may require review.

Quick Start

Use the semantic-git skill to analyze the blast radius of the changes in the current branch.

Frequently Asked Questions about semantic-git

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

FAQPage Schema
How do I analyze the blast radius of code changes before merging a refactor?▼

To analyze the blast radius of code changes, you can trace downstream dependencies of modified functions and classes to identify affected callers and components requiring review before a merge.

What is a structural diff and how does it differ from a standard Git diff?▼

A structural diff identifies changes at the code entity level, such as functions and classes, rather than showing line-by-line text changes, making it easier to understand meaningful modifications and their impact.

How do I identify which functions and classes were changed in a Git branch?▼

You identify changed functions and classes by running a semantic diff analysis on the branch, which inspects structural code changes and their downstream impact beyond standard line-level Git diffs.

Do I need a specific command-line interface to perform semantic git analysis?▼

Yes, semantic git analysis requires the sem command-line interface to inspect semantic diffs, dependencies, context, blame, history, and file entities when investigating changes.

Can I use entity-level blame and history for debugging code changes?▼

Yes, you can inspect entity-level blame, surrounding context, and history to investigate changes, allowing you to review structural modifications and trace dependencies during debugging.

What is the best way to review code changes beyond line-level Git diffs?▼

The best way to review code changes beyond line-level Git diffs is applying structural analysis to inspect changed code entities, trace downstream dependencies, and determine the blast radius across the codebase.

Related Skills

Explore More Software Engineering Skills→
locdinh209locdinh209

git-operations

Automates Git repository operations including commits, branches, diffs, and staging for AI agents.

Community
Intermediate
0xHoneyJar0xHoneyJar

triage

Triages user signals and error reports to identify affected code paths and estimate blast radius.

Official
Intermediate
zerAdazerAda

bmad-qa-generate-e2e-tests

Generate end-to-end API and UI tests for identified application features.

Community
Advanced
demon24rudemon24ru
8

trace-impact

Trace code change impact and blast radius across registered repositories.

Community
Advanced