fixme-research

Identify root causes and generate fix strategies from codebase analysis.

Updated Feb 18, 2026

Search Tags:#planning #research #investigation #codebase #dependencies #references #root-cause

Ready to run

npx skills add https://github.com/denis-pingin/fixme --skill fixme-research

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fixme-research
Source: https://github.com/denis-pingin/fixme/tree/main/.claude/skills/fixme-research
Command: npx skills add https://github.com/denis-pingin/fixme --skill fixme-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams understand an issue by locating relevant files, tracing dependencies, and outlining potential approaches without changing code.

Core Features & Use Cases

Explore the codebase around a known issue to locate affected files, trace references, and assess impact.
Generate a set of approach candidates with pros/cons for fixes.
Produce a structured research output to guide engineering decisions.

Quick Start

Provide a task description and optionally an investigation path to generate a comprehensive research report.

Frequently Asked Questions about fixme-research

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

FAQPage Schema

What is codebase research for root cause analysis?▼

Codebase research for root cause analysis involves examining affected files, tracing dependencies, and summarizing the underlying issue to guide the assessment of fix strategies without making actual code changes.

How do I investigate a known issue in a codebase?▼

To investigate a known issue, provide a task description and an optional investigation path to explore the codebase, locate affected files, trace references, and generate a structured research report.

Can I generate fix strategy candidates without changing code?▼

Yes, you can generate fix strategy candidates without changing code by applying investigation findings to assess approaches and outline pros and cons during a dedicated research phase.

Does this approach work for tracing dependencies and references?▼

This approach works for tracing dependencies and references by exploring the codebase around known issues to locate affected files, assess impact, and surface structured fix strategies.

What is the best way to assess impact for a software bug?▼

The best way to assess impact for a software bug is to explore the codebase around the affected areas, trace references, and produce a structured research output to guide engineering decisions.

When should I not use a research phase for codebase investigation?▼

You should not use a research phase for codebase investigation when you need actual code changes, as this approach only relies on provided task descriptions and available findings to outline strategies.