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

risk-assessment

Analyze codebase risk by cross-referencing git history with semantic search.

11|3|Updated Jan 29, 2026
Search Tags:#refactoring#code-quality#risk-assessment#technical-debt#hotspot-analysis
One-click install
npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill risk-assessment-artk0de
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: risk-assessment
Source: https://github.com/artk0de/TeaRAGs-MCP/tree/main/.claude-plugin/tea-rags/skills/risk-assessment
Command: npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill risk-assessment-artk0de

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of blind code navigation by identifying high-risk areas such as bug attractors, fragile legacy code, and toxic silos that standard semantic search misses.

Core Features & Use Cases

  • Multi-dimensional Risk Scanning: Uses four distinct reranking presets to surface bugs, hotspots, tech debt, and dangerous code.
  • Structural Analysis: Integrates with codegraph to identify blast-radius hubs and circular dependencies.
  • Use Case: Use this when you need to audit a specific subsystem for technical debt or identify which modules are most likely to cause regressions during a major refactor.

Quick Start

Run the risk-assessment skill on the authentication subsystem to identify critical bug magnets and structural hotspots.

Frequently Asked Questions about risk-assessment

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

FAQPage Schema
How do I identify high-risk code hotspots before a major refactoring project?▼

You can identify high-risk code hotspots by cross-referencing git history signals with semantic search results. This approach targets bug attractors, fragile legacy code, and structural coupling points that standard semantic searches typically miss.

What is the best way to find technical debt and bug attractors in a specific subsystem?▼

The best way to find technical debt and bug attractors in a specific subsystem is using multi-dimensional risk scanning. This method applies four distinct reranking presets to evaluate churn, bug-fix rates, and architectural dependencies without manual git log inspection.

Does this risk assessment tool require manual git log inspection to evaluate code quality?▼

No, evaluating code quality does not require manual git log inspection. The risk assessment process integrates with TeaRAGs-MCP tools to automatically evaluate churn, bug-fix rates, and architectural dependencies directly from the codebase.

Can I detect circular dependencies and blast-radius hubs during a codebase audit?▼

Yes, you can detect circular dependencies and blast-radius hubs during a codebase audit through structural analysis. The risk assessment integrates with codegraph capabilities to identify these critical architectural dependencies and structural coupling points.

When should I not use semantic search alone for navigating legacy code?▼

Semantic search alone should not be used for navigating legacy code when you need to uncover toxic silos and fragile modules. It fails to cross-reference historical git signals, meaning it misses critical bug attractors and high-churn risk zones.

Related Skills

Explore More Software Engineering Skills→
j4hr3nj4hr3n

recon

Analyze git history and project metrics to generate a codebase health report.

Community
Advanced
sumilee-pcusumilee-pcu

tech-debt

Scan source code for TODOs and complexity hotspots to manage technical debt.

Community
Intermediate
Prathmesh2000Prathmesh2000
1

dependency-mapper

Map and analyze codebase dependencies to detect circular dependencies and coupling hotspots.

Community
Advanced
nikhillinitnikhillinit

tech-debt-tracker

Detect and prioritize technical debt with configurable thresholds and SQALE metrics.

Community
Advanced