skills.rest
uoyoCsharp
uoyoCsharpCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

mvt-bug-detect

Analyze software defects to confirm bugs, identify root causes, and assess impact.

19|Updated Feb 12, 2026
Search Tags:#debugging#root cause analysis#stack trace#bug detection#git analysis#impact assessment#read-only diagnosis
One-click install
npx skills add https://github.com/uoyoCsharp/My-Virtual-TechTeam --skill mvt-bug-detect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mvt-bug-detect
Source: https://github.com/uoyoCsharp/My-Virtual-TechTeam/tree/main/.claude/skills/mvt-bug-detect
Command: npx skills add https://github.com/uoyoCsharp/My-Virtual-TechTeam --skill mvt-bug-detect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you investigate suspected software bugs without jumping straight into fixes. It turns vague failure reports, error messages, stack traces, and behavioral issues into a structured diagnosis covering whether the bug is real, what likely caused it, how severe it is, and what parts of the codebase may be affected.

Core Features & Use Cases

  • Structured bug investigation: Confirms whether an issue is verified, likely, inconclusive, or not actually a bug.
  • Root cause analysis: Extracts signals from stack traces, file paths, error text, and recent code changes to generate and test evidence-based hypotheses.
  • Impact assessment: Classifies severity, identifies affected modules and user flows, and looks for similar patterns elsewhere in the codebase.
  • Use case: When a production error appears after a recent change, use this Skill to localize the failure, connect it to relevant files and commits, and decide whether you need a direct fix, a design change, or requirement re-analysis.

Quick Start

Ask the AI to use mvt-bug-detect on a specific error, stack trace, or reproduction scenario so it can analyze the cause and report the impact without modifying code.

Frequently Asked Questions about mvt-bug-detect

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

FAQPage Schema
How do I find the root cause of a bug from a stack trace without modifying code?▼

Root cause analysis from a stack trace requires extracting signals, localizing code, and inspecting git history to verify hypotheses. This diagnostic process confirms bugs and assesses impact while keeping the codebase completely read-only.

What is the best way to investigate vague behavioral regressions after a recent code change?▼

Investigating vague behavioral regressions involves structured signal extraction from recent repository changes, generating evidence-based hypotheses, and classifying severity. This approach connects failures to specific files and commits to determine if a design change or requirement re-analysis is needed.

Can I use git history inspection to assess the impact and severity of a suspected software defect?▼

Git history inspection helps assess suspected software defects by identifying affected modules and user flows. It classifies severity and searches for similar patterns elsewhere in the codebase to provide a structured diagnostic report.

Does bug diagnosis work for error messages and reproduction steps without applying direct fixes?▼

Bug diagnosis works for error messages and reproduction steps by confirming whether issues are verified, likely, inconclusive, or not bugs. It generates a read-only diagnostic report detailing root causes and impact without applying direct fixes.

When should I not use a read-only diagnostic approach for debugging?▼

A read-only diagnostic approach should not be used when immediate code modification is required. It is designed strictly for investigation, confirming bugs, and assessing impact, meaning it will not apply patches or resolve the error directly.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
e-xodee-xode
3

review

Review branch, PR, or uncommitted diffs and output a severity-categorized markdown report.

Official
Intermediate
Haohao-endHaohao-end
779

qa-only

Produce report-only QA evidence with reproduction steps and screenshots.

Community
Basic
devMoezdevMoez
1

node-inspect-debugger

Debug Node.js runtime failures via V8 inspector breakpoints and CDP.

Community
Intermediate