Can I use it on existing uncommitted changes?

Yes, if you run the skill without arguments, it detects uncommitted changes compared to main and automatically packages them into a new fix branch.

Does it require the GitHub CLI?

Yes, the final stage uses the 'gh' CLI to create draft Pull Requests containing the captured verification logs and failure evidence.

Why does it require tests to fail on the main branch?

Requiring a test to fail on main before applying a fix ensures the test accurately reproduces the bug, providing objective proof that the fix actually works.

What specialized agents are involved in the process?

The workflow uses three specialized personas: a Test Engineer (Georg) for MREs, a Coder (Sergei) for implementation, and a Reviewer (Patrick) for quality assurance.

How does this skill handle multiple bugs at once?

It utilizes git worktrees to create separate, isolated working directories for each branch, allowing the agent to process multiple fixes in parallel.

Automated Bug Fix & PR Workflow

Name: Automated Bug Fix & PR Workflow
Author: krystophny

bykrystophny

•

Herramientas para Desarrolladores

Automates the entire bug fix lifecycle from MRE creation to PR submission using parallel git worktrees and AI agents.

The pr skill streamlines the bug-fixing process by automating branch creation, test development, and PR generation. It leverages git worktrees to allow developers to work on multiple fixes in parallel without manual context switching. The workflow enforces a rigorous 'test-first' methodology where specialized agents create a minimal reproducing test that must fail on the main branch and pass after the fix. It concludes by generating a comprehensive Pull Request using the GitHub CLI, complete with console logs as verification evidence and technical debt checks.