skills.rest
mathur-exe
mathur-exeCOMMUNITY
Explore all skills by this author →
Website𝕏@gaurang__mathurGitHub

problem-analyzer

Analyze software problems by locating affected files, root causes, and minimal fixes.

Updated Sep 1, 2025
Search Tags:#debugging#codebase#triage#analyze#root-cause#bug-fix#problem-analysis
One-click install
npx skills add https://github.com/mathur-exe/annotation-notes --skill problem-analyzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: problem-analyzer
Source: https://github.com/mathur-exe/annotation-notes/tree/main/PaperNotes/dotfiles/codex/skills/problem-analyzer
Command: npx skills add https://github.com/mathur-exe/annotation-notes --skill problem-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze a problem by tracing affected files, deducing root causes, and proposing minimal, safe fixes.

Core Features & Use Cases

  • Identify all files/modules implicated by an issue and show why each is relevant.
  • Explain root causes: what changed, how it propagates to failure, and environmental factors.
  • Propose minimal, safe fixes with code-level steps, potential side effects, and tests to add or update.

Quick Start

Describe the issue and return a prioritized plan of affected files, root causes, and a minimal fix.

Frequently Asked Questions about problem-analyzer

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

FAQPage Schema
How do I trace a bug to its root cause in a large codebase?▼

Root-cause analysis for debugging involves identifying all affected files and modules, explaining what changed, and mapping how failures propagate through the system to pinpoint the exact origin of the issue.

What is the best way to propose a minimal safe fix for a software bug?▼

Proposing a minimal safe fix requires outlining code-level remediation steps, identifying potential side effects, and specifying tests to add or update, ensuring the bug fix is incremental and verifiable.

How do I triage an issue and identify all affected files in my software project?▼

Triage and issue analysis involve scanning the software project to identify all implicated files and modules, explicitly showing why each component is relevant to the failure and establishing traceability for debugging.

Can I get a reproducible root-cause reasoning plan for incremental remediation?▼

Yes, reproducible root-cause reasoning generates a prioritized plan that traces component changes and environmental factors, enforcing traceability and delivering a safe, testable fix plan for incremental remediation.

Does problem analysis require specific dependencies to locate affected modules?▼

No specific dependencies are required to locate affected modules. The analysis operates directly on the codebase to trace issues, identify implicated files, and deduce root causes without external tool constraints.

Related Skills

Explore More Software Engineering Skills→
useautumnuseautumn
2.6k

linear-ticket

Create structured Linear tickets with GitHub permalinks from engineering ideas.

Official
Basic
Sheldon-92Sheldon-92
3

Testing

Execute test suites and report failures with coverage metrics.

Community
Intermediate
CERTCCCERTCC
21

acquire-codebase-knowledge

Analyze project files and directory structures to document codebase architecture and dependencies.

Official
Intermediate
saschadudkin-sketchsaschadudkin-sketch

code-review

Automate code review for rezidence4/DomHub repository changes.

Community
Advanced