skills.rest
benjaminfauchald
benjaminfauchaldCOMMUNITY
Explore all skills by this author →
GitHub

bug

Automate bug fixes with GitHub issues, isolated worktrees, tests, and PRs.

Updated Aug 23, 2026
Search Tags:#git#github#worktree#pr#rails#bugfix#issue-tracking
One-click install
npx skills add https://github.com/benjaminfauchald/Tracklister --skill bug-benjaminfauchald
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug
Source: https://github.com/benjaminfauchald/Tracklister/tree/main/.claude/skills/bug
Command: npx skills add https://github.com/benjaminfauchald/Tracklister --skill bug-benjaminfauchald

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a disciplined, repeatable bug-fix workflow that prevents conflicting sessions, missing issue tracking, and unsafe repository inspections by requiring a ticket-first, isolated worktree-first process.

Core Features & Use Cases

  • Enforced Workflow Sequencing: Requires pre-checks for existing worktrees, creation of a GitHub issue, and use of EnterWorktree before any code inspection or edits.
  • Safety and Performance Guards: Provides checks for worktree isolation, branch-name uniqueness, performance risk review, anti-pattern verification, and explicit rules about commits and PR practices.
  • Use Case: A developer fixing a Rails bug creates an issue, spawns an isolated worktree, investigates and fixes the defect, runs targeted tests, pushes a branch, opens a PR, and documents the incident in Obsidian.

Quick Start

Describe the bug to create the GitHub issue, then run EnterWorktree with a derived branch name and follow the prescribed checks to investigate, fix, test, commit, push, and open a PR.

Frequently Asked Questions about bug

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

FAQPage Schema
How do I fix a Rails bug using an isolated git worktree?▼

A disciplined bug-fix workflow prevents conflicting sessions by enforcing ticket creation and isolated git worktrees before code inspection, ensuring safe repository edits and tracked issue resolution.

What is the best way to enforce issue tracking before fixing a GitHub bug?▼

Enforcing issue tracking before fixing a GitHub bug requires a sequential workflow that mandates creating a GitHub issue and spawning an isolated worktree prior to any local code inspection or edits.

How do I create a GitHub PR from a git worktree for a bugfix?▼

Creating a GitHub PR from a git worktree involves running targeted tests on your local fixes, pushing the isolated branch, opening the PR, and then synchronizing the incident documentation.

Does this bugfix workflow work with existing git worktrees?▼

Yes, the bugfix workflow works with existing git worktrees by running sequential pre-checks for active worktrees and verifying branch-name uniqueness before you begin any code inspection.

What checks are required before opening a PR for a Rails bugfix?▼

Before opening a PR for a Rails bugfix, required checks include worktree isolation, branch-name uniqueness, performance risk review, anti-pattern verification, and running targeted tests.

Related Skills

Explore More Software Engineering Skills→
RanFRRanFR
2

pr-creator

Automates GitHub Pull Request creation using Git CLI and gh auth workflows.

Community
Intermediate
yongwoonyongwoon
8

ywc-create-pr

Automate Git feature branch commits, security validation, and draft pull request creation.

Community
Advanced
dlt-hubdlt-hub
5.7k

worktree-from-issue

Create a git worktree and per-issue branch for a GitHub issue.

Official
Advanced
HardyLiu6HardyLiu6

using-git-worktrees

Create isolated git worktrees for feature branch development.

Community
Advanced