skills.rest
grafana
grafanaOFFICIAL
Explore all skills by this author →
Website𝕏@grafanaGitHub

bugfix

Coordinate bug fixes in Grafana Pathfinder using isolated git worktrees and phase-driven triage.

19|31|Updated May 29, 2025
Search Tags:#git#subagents#worktree#robustness#bugfix#test-driven-development#pathfinder
One-click install
npx skills add https://github.com/grafana/grafana-pathfinder-app --skill bugfix-grafana
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bugfix
Source: https://github.com/grafana/grafana-pathfinder-app/tree/main/.cursor/skills/bugfix
Command: npx skills add https://github.com/grafana/grafana-pathfinder-app --skill bugfix-grafana

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables structured, isolated bug fixes for robustness problems in the Grafana Pathfinder ecosystem by driving a phase-based workflow, using git worktrees, and leveraging subagents to guide triage, exploration, and verification.

Core Features & Use Cases

  • Isolate each bugfix in its own worktree to prevent cross-contamination between fixes.
  • Follow a phase-driven workflow (triage, code investigation, test design, and validation) with documented prompts and artifacts.
  • Leverage dedicated subagents defined in SUBAGENTS.md to perform code exploration and related-issues analysis.
  • Maintain auditable processes and guards against scope creep through strict commit and testing discipline.

Quick Start

Open a robustness issue and start the /bugfix workflow to create an isolated worktree and spawn focused subagents.

Frequently Asked Questions about bugfix

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

FAQPage Schema
How do I isolate robustness bug fixes in git to prevent cross-contamination?▼

Robustness bug fixes are isolated by creating dedicated git worktrees for each issue, preventing cross-contamination between concurrent fixes while maintaining a phase-driven workflow for triage and validation.

What is test-driven development for robustness bugs and how does it enforce failing tests?▼

Test-driven development for robustness bugs enforces writing failing tests before applying fixes, ensuring the defect is captured and validated before the code is changed to preserve architecture boundaries.

How do I structure code investigation and triage for complex robustness issues?▼

Code investigation and triage are structured through a phase-driven workflow using dedicated subagents to explore code, analyze related issues, and document prompts and artifacts for future maintainers.

Can I use subagents to explore code and analyze related robustness issues?▼

Yes, subagents defined in SUBAGENTS.md are leveraged to perform code exploration and related-issues analysis, guiding the triage phase to maintain auditable processes and prevent scope creep.

Does the bugfix workflow require isolated git worktrees to maintain auditable commits?▼

Yes, the workflow requires isolated git worktrees to maintain strict commit and testing discipline, preventing scope creep and ensuring every robustness fix produces auditable, documented steps.

When do I need a phase-driven workflow for robustness bug fixes?▼

A phase-driven workflow is needed for open robustness issues requiring structured exploration, test design, and validation, ensuring architecture boundaries are preserved and steps are documented for future maintainers.

Related Skills

Explore More Software Engineering Skills→
havingautismhavingautism
190

using-git-worktrees

Create isolated git worktrees for feature development.

Community
Intermediate
Likas07Likas07

test-driven-development

Enforce the RED-GREEN-REFACTOR cycle by writing failing tests before implementation code.

Community
Advanced
avav
3.2k

bughunt

Automate bug discovery, triage, fixing, and auditing in codebases.

Community
Advanced
ssiumhassiumha
9

tdd-practices

Guide developers through the RED-GREEN-REFACTOR TDD cycle.

Community
Advanced