receiving-code-review

Analyze structural and historical impact of proposed code changes.

11|3|Updated Jan 29, 2026

Search Tags:#code review #refactoring #technical debt #impact analysis #git history #blast radius

Ready to run

npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill receiving-code-review-artk0de

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/artk0de/TeaRAGs-MCP/tree/main/.claude-plugin/dinopowers/skills/receiving-code-review
Command: npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill receiving-code-review-artk0de

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the common pitfall of blindly accepting code review suggestions that may introduce regressions or technical debt by providing concrete impact data before you commit to changes.

Core Features & Use Cases

Blast Radius Assessment: Automatically calculates the impact of proposed renames, refactors, or moves using git history and import signals.
Call Route Tracing: Visualizes the ripple effects of changes across complex call paths to identify high-impact chokepoints.
Test Binding Identification: Surfaces existing tests that are at risk due to structural changes, ensuring you understand the cost of implementation before agreeing.

Quick Start

Analyze the impact of the reviewer's suggestion to rename the current function by invoking the receiving-code-review skill with the target symbol and intent.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema

How do I analyze the blast radius of a code refactoring suggestion?▼

Blast radius assessment calculates the impact of proposed renames or refactors by evaluating import counts and git history churn to determine the structural impact of changes before you commit them.

What is code review impact analysis and when do I need it?▼

Code review impact analysis is the process of evaluating the structural and historical impact of proposed code changes. You need it when reviewing refactoring or architectural modifications to prevent introducing regressions or technical debt.

How do I trace call routes to identify high-impact chokepoints during a code review?▼

You trace call routes by visualizing the ripple effects of structural changes across complex call paths. This identifies high-impact chokepoints and surfaces existing tests at risk due to the modification.

Does the code review impact analysis require a specific MCP server integration?▼

Yes, the impact analysis requires integration with the TeaRAGs MCP server to evaluate import counts, churn, and ownership metrics for specific symbols or call routes during code review decisions.

How do I identify tests at risk before accepting a code reviewer's rename suggestion?▼

You identify tests at risk by performing test binding identification, which surfaces existing tests that are vulnerable to structural changes and helps you understand the implementation cost before agreeing to the suggestion.