Automate bug fixing workflows from reproduction to GitHub PR.
npx skills add https://github.com/pekral/cursor-rules --skill auto-fix-bug
Please help me install this Agent Skill. Skill: auto-fix-bug Source: https://github.com/pekral/cursor-rules/tree/main/skills/auto-fix-bug Command: npx skills add https://github.com/pekral/cursor-rules --skill auto-fix-bug
This Skill automates the end-to-end bug fixing workflow, from reproducing a bug and adding a regression test to implementing the minimal fix and delivering a GitHub Pull Request.
Provide the bug description and reproduction steps; the skill will create a fix branch, commit changes with Conventional Commits, push, and open a GitHub PR.
High-intent search queries and answers about installing and using this skill.
Automating a bug fix workflow involves reproducing the issue, adding a regression test, creating a dedicated branch, committing with Conventional Commits, and pushing a GitHub PR. This skill orchestrates that end-to-end process using tool-assisted automation and optional gh CLI integration.
Structuring commits during an automated bug fix requires using Conventional Commits on a dedicated fix branch. This ensures clear, standardized commit history across the workflow, from regression testing through the final code implementation before opening the pull request.
You do not need the gh CLI installed to automate opening a GitHub pull request, though it is used for PR automation when available. If the CLI is absent, the workflow provides clear manual fallback steps to complete the push and PR creation.
Regression testing fits into an automated git branching workflow by validating the bug reproduction before the fix is applied. The workflow creates a dedicated branch, adds the regression test, implements the minimal fix, and commits everything using Conventional Commits.
You can use this automated bug fixing process even without direct GitHub access. The workflow enforces a minimal process with clear fallback steps for manual branch pushing and PR creation if the gh CLI automation cannot access GitHub.
Creating a conventional commit bug fix PR requires providing bug reproduction steps, creating a fix branch, writing a regression test, and implementing the fix. The workflow then commits using Conventional Commits and opens a PR via gh CLI or manual fallback.
Synthesys-LabCreate a GitHub development branch for a given issue number.
SeanHoggRebase a GitHub Pull Request onto main, fix review findings, run gates, and push.
ketronkowskiValidate Git commit messages against conventional commit formatting rules.
octave-commonsCoordinates Git branching, commits, conflict resolution, rebasing, and GitHub CLI pull requests across teams.
