skills.rest
kelsi-andrewss
kelsi-andrewssCOMMUNITY
Explore all skills by this author →
GitHub

find-bug

Generate structured root-cause analyses for software bugs using Gemini's large-context tool.

1|Updated Feb 21, 2026
Search Tags:#debugging#gemini#root-cause#story-creation#epic-tracking#find-bug
One-click install
npx skills add https://github.com/kelsi-andrewss/claude-multi-agent-pipeline --skill find-bug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: find-bug
Source: https://github.com/kelsi-andrewss/claude-multi-agent-pipeline/tree/main/skills/find-bug
Command: npx skills add https://github.com/kelsi-andrewss/claude-multi-agent-pipeline --skill find-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnosing software bugs can be time-consuming and error-prone; this skill leverages Gemini's large-context MCP tool to produce a structured root-cause analysis with location, contributing factors, reproduction steps, and a fix direction.

Core Features & Use Cases

  • Structured diagnosis: Generates a comprehensive root-cause analysis including most likely location, contributing factors, reproduction steps, and a suggested fix direction.
  • Context-rich exploration: Integrates Gemini MCP's large-context analysis to handle complex bugs from symptoms, logs, and user reports.
  • Epic/story integration: Creates and tracks a bug diagnosis plan and associated story within the project's epic hierarchy.

Quick Start

Describe the bug symptom after /find-bug to begin the diagnostic workflow.

Frequently Asked Questions about find-bug

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

FAQPage Schema
How do I diagnose a software bug from logs and error reports?▼

Diagnosing a software bug from logs and error reports requires generating a structured root-cause analysis. This skill uses Gemini's large-context to process symptoms, identify the likely location, and suggest a fix direction.

What is root-cause analysis in software debugging?▼

Root-cause analysis in software debugging identifies the most likely location of a bug, its contributing factors, reproduction steps, and a suggested fix direction. This skill leverages Gemini's large-context to generate this structured diagnosis.

How do I create an epic and tracking story for a bug fix?▼

Creating an epic and tracking story for a bug fix requires assigning the diagnosis to your project hierarchy. This skill automatically guides epic assignment and generates a bug-diagnosis plan file along with a tracking story.

Can I use Gemini large-context for complex bug diagnosis?▼

Gemini large-context can be used for complex bug diagnosis by loading the mcp__gemini__find_bug tool. It processes detailed symptom descriptions, logs, and user reports to produce a comprehensive root-cause analysis.

Does the find-bug skill require specific dependencies to work?▼

The find-bug skill requires loading the mcp__gemini__find_bug tool to function, with an optional --model flag for configuration. It has no other dependencies and outputs a diagnosis plan file and tracking story.

Related Skills

Explore More Software Engineering Skills→
LynxLabVNLynxLabVN

dogfood

Guide systematic exploratory QA testing of web applications with browser tools.

Official
Advanced
ncptuanncptuan

bmad-sprint-planning

Generate sprint-status.yaml from markdown epic and story files.

Community
Advanced
luissimon96luissimon96

graph-fix-bugs

Guide structured bug fixing with reproduce, analyze, implement, and verify steps.

Community
Advanced
allanninalallanninal
1

root-cause-tracing

Trace stack traces and logs to identify root causes of software failures.

Community
Intermediate