skills.rest
artk0de
artk0deCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Analyze git history and dependency signals to identify regression risks in edited files.

11|3|Updated Jan 29, 2026
Search Tags:#code review#mcp#impact analysis#regression testing#git history#blast radius
One-click install
npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill verification-before-completion-artk0de
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/artk0de/TeaRAGs-MCP/tree/main/.claude-plugin/dinopowers/skills/verification-before-completion
Command: npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill verification-before-completion-artk0de

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the common issue of agents claiming work is complete while leaving broken dependencies or collateral damage in the codebase.

Core Features & Use Cases

  • Collateral-Damage Scan: Automatically identifies high-risk files that could break due to your recent edits by analyzing import counts, churn, and ownership.
  • Targeted Verification: Provides a prescriptive list of test scenarios for high-blast-radius files to ensure your changes are truly stable.
  • Use Case: Before committing a refactor to a core utility file, use this skill to identify which dependent modules are at risk and receive a targeted list of tests to run to ensure no regressions were introduced.

Quick Start

Run the verification-before-completion skill to scan your recent changes for potential collateral damage and identify necessary tests before finalizing your work.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema
How do I prevent regressions when refactoring core utility files?▼

Blast radius analysis identifies high-risk files that could break from your recent edits by querying git history and dependency signals, preventing collateral damage and broken imports in downstream modules.

How do I identify the blast radius of code changes before committing?▼

You can identify the blast radius of code changes by analyzing import counts, file churn, and git history, which highlights high-risk dependent modules vulnerable to your recent edits.

Does impact analysis for code changes require any specific integrations?▼

Yes, performing semantic search and impact reranking for code changes requires integration with TeaRAGs-MCP to accurately analyze the codebase and identify potential collateral damage.

What is the best way to verify code stability in high-churn areas?▼

The best way to verify code stability in high-churn areas is to scan recent changes for potential collateral damage and execute a prescriptive list of test scenarios targeting high-blast-radius files.

Why do agents leave broken dependencies after claiming code work is complete?▼

Agents leave broken dependencies when they lack automated collateral-damage scanning, failing to analyze import counts and churn to identify downstream modules at risk from recent edits.

When should I run a collateral-damage scan on my codebase?▼

You should run a collateral-damage scan before finalizing a refactor or completing work on core utility files, ensuring your code changes do not introduce regressions in high-blast-radius areas.

Related Skills

Explore More Software Engineering Skills→
artk0deartk0de
11

add-derived-signal

Implement custom normalized ranking signals for TeaRAGs code reranking.

Community
Advanced
jpoleyjpoley
50

patch-engineer

Validate security patch quality and regression risk for code changes.

Community
Advanced
jmolzjmolz

source-command-review

Automate code review and regression suite execution for software development workflows.

Community
Advanced
artk0deartk0de
11

receiving-code-review

Analyze structural and historical impact of proposed code changes.

Community
Advanced