sem

Analyze code changes and dependencies to assess impact and risk.

4|1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/gtheys/pi-my-rifle-ext --skill sem-gtheys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sem
Source: https://github.com/gtheys/pi-my-rifle-ext/tree/main/skills/sem
Command: npx skills add https://github.com/gtheys/pi-my-rifle-ext --skill sem-gtheys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Entity-aware code change analysis using the pi-sem tools helps you understand exactly what changed, why it changed, and how it might affect the rest of the codebase.

Core Features & Use Cases

  • Focused context for a single entity (function, method, class, or config) to quickly grasp changes without reading the entire file.
  • Blast radius and impact analysis to identify affected tests, dependent modules, and potential risk.
  • Semantic diff-guided review workflow that complements raw diffs with entity-level insights and historical context.
  • Structured review guidance for commits, branches, and PRs to improve review quality and speed.

Quick Start

Provide a function or class name and ask for focused context with sem_context, then request blast radius with sem_impact to understand broader effects.

Frequently Asked Questions about sem

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

FAQPage Schema
How do I analyze the semantic impact of code changes across modules?

Semantic code change analysis identifies exactly what changed and why by extracting focused context for specific functions or classes, helping you grasp modifications without reading the entire file.

What is the best way to estimate the blast radius of a git diff?

Estimating the blast radius of a git diff involves using semantic impact analysis to identify affected tests, dependent modules, and potential risks across the codebase.

How do I review a pull request without reading the entire file?

You can review a pull request by requesting focused context for a single entity like a function or class, allowing you to quickly grasp changes and entity-level insights without reading the whole file.

Can I use semantic diff interpretation for branch and working tree reviews?

Yes, semantic diff interpretation supports structured review guidance for branches and working trees, complementing raw diffs with historical context and entity-level insights to improve review speed.

Does semantic code change analysis require specific dependencies to work?

No, semantic code change analysis operates independently without requiring external dependencies, using internal tools to extract entity context and estimate impact for code reviews.