" --body "<body>"` **PR title:** Same as commit subject (without scope is ok); keep it short. **PR body template (fill it):** - **What/Why:** 1–3 bullets. - **Repro:** Steps or link to failing case. - **Fix:** What changed. - **Tests:** Exact commands run. - **Risk:** Any edge cases or migration notes. - **Links:** `closes #ID` (if applicable). ### 2.9 Final verification **Do:** - Ensure the PR is open and points to the correct base branch. - Ensure the branch contains commit(s) and CI can run. - When creating a commit or PR, never add a signature, but leave only the person's signature! --- ## 3. Guardrails **Do not:** - Commit secrets, tokens, or credentials. - Change formatting project-wide. - “Fix” unrelated warnings opportunistically. **Do:** If you touch production-critical paths, add extra tests. --- ## 4. If `gh` Is Unavailable **Do:** 1. Push the branch. 2. Print instructions: PR URL format hint (repo + compare branch), base branch to select, title/body to paste. --- Source attribution: pekral Original project: https://github.com/pekral/cursor-rules/blob/24214b75cd351b83609811ec39b25925582c7aa3/skills/auto-fix-bug/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Dave AI. ## Upstream license notice MIT License Copyright (c) 2025 Petr Král Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Dave AI resource metadata Creator / publisher: pekral Original project: https://github.com/pekral/cursor-rules/blob/24214b75cd351b83609811ec39b25925582c7aa3/skills/auto-fix-bug/SKILL.md Attribution basis: Recovered original package and original project license at a pinned revision Fields of work: Development & Engineering, Product Management, Customer Support Roles: Backend Developer, DevOps / SRE, Product Manager, QA / Test Engineer, Technical Support Specialties: Backend, Git Tools: GitHub Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: e6cdaf2da60c8512d24ebd349ed14109ce593f7cd3d9ea41cb52f8293444fd31 Metadata reviewed: 2026-10-27 This metadata supersedes earlier Dave AI catalog attribution. Original instruction and supporting files are preserved.

--- name: auto-fix-bug description: Fix a reported bug end-to-end: reproduce it, add a regression test, implement the minimal fix, create a new git branch, commit using Conventional Commits, push, and open a GitHub PR (prefer gh CLI). Use when the user asks to fix a bug and wants a PR created. --- # Auto Bugfix → Branch + Commit + PR (GitHub) **Role:** Fix a reported bug end-to-end and deliver a new branch, commit(s), and an open GitHub Pull Request. **Non-negotiable outcome:** When this skill is used, you MUST deliver: 1. A **new branch** with the fix. 2. At least one **commit** (Conventional Commits). In the commit message, link the issue (e.g. `fixes #123` or `fixed #123`). 3. A **GitHub Pull Request** opened from that branch, **linked to the issue**: the PR body MUST contain `Closes #` or `Fixes #` so GitHub links the PR to the issue and can auto-close it when merged. If you cannot create the PR automatically (missing permissions, no `gh`), push the branch and output the exact manual steps to create the PR in the GitHub UI; the PR body must still include the issue link (Closes #N). --- ## 1. Inputs to Collect Prefer no back-and-forth. If missing, infer from repo conventions; otherwise ask only the minimum. **Collect:** - Bug description and expected behavior. - How to reproduce: steps, endpoint, failing test, or error log. - Related issue/PR link (if exists). - Target base branch (default: `master` or `main` based on repo). --- ## 2. Workflow (Strict Order) ### 2.1 Reproduce the bug **Do:** - Identify the failing behavior locally (tests, reproduction steps, logs). - If a test suite exists, find the closest relevant test and run it first. ### 2.2 Add a regression test **Do:** - Add or adjust a test that fails **before** the fix and passes **after** the fix. - Keep the test minimal and focused on the reported bug. ### 2.3 Create a new branch **Branch naming:** Prefer `fix/` or `bugfix/-` if a ticket id exists. **Do:** - Run `git status` (must be clean, or explicitly explain what you are doing). - Run `git checkout -b fix/` (or equivalent). ### 2.4 Implement the minimal fix **Do:** - Smallest change that makes the regression test pass. - Avoid drive-by refactors unless required to fix the bug. - Keep public APIs stable unless the bug is explicitly an API change. ### 2.5 Run checks locally **Do:** Run the fastest relevant subset first, then the full suite when reasonable. - Tests: single file or targeted, then full. - Lints and static analysis if available. - Do code review defined in .cursor/skills/code-review/SKILL.md, if there are not critical errors you can continue. If something fails, fix it before committing. ### 2.6 Commit (Conventional Commits) **Rules:** - Follow Conventional Commits. - When creating a commit or PR, never add a signature, but leave only the person's signature! - For bugfixes default to `fix:` or `fix(scope):`. - Message should describe user-visible outcome, not implementation detail. - The commit message should be as short as possible but should accurately describe the current changes! - Add commit message by defined rules and GitHub automatically creates a link to the mentioned issue. For example, if your issue number is 123 , you can mention it in your PR like this: #123 - List all the sources you found that helped you fix the error, and always write a simple report on how and why the error was fixed in the current way. **Examples:** - `fix(auth): prevent token refresh race condition` - `fix: handle null customer id in webhook handler` **Do:** - `git add -A` - `git commit -m "fix():

"` ### 2.7 Push branch **Do:** - `git push -u origin fix/` Do not force-push unless the user explicitly asks. ### 2.8 Create PR in GitHub **Prefer GitHub CLI:** - `gh pr create --base --head fix/ --title "" --body "<body>"` **PR title:** Same as commit subject (without scope is ok); keep it short. **PR body template (fill it):** - **What/Why:** 1–3 bullets. - **Repro:** Steps or link to failing case. - **Fix:** What changed. - **Tests:** Exact commands run. - **Risk:** Any edge cases or migration notes. - **Links:** `closes #ID` (if applicable). ### 2.9 Final verification **Do:** - Ensure the PR is open and points to the correct base branch. - Ensure the branch contains commit(s) and CI can run. - When creating a commit or PR, never add a signature, but leave only the person's signature! --- ## 3. Guardrails **Do not:** - Commit secrets, tokens, or credentials. - Change formatting project-wide. - “Fix” unrelated warnings opportunistically. **Do:** If you touch production-critical paths, add extra tests. --- ## 4. If `gh` Is Unavailable **Do:** 1. Push the branch. 2. Print instructions: PR URL format hint (repo + compare branch), base branch to select, title/body to paste. --- Source attribution: pekral Original project: https://github.com/pekral/cursor-rules/blob/24214b75cd351b83609811ec39b25925582c7aa3/skills/auto-fix-bug/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Dave AI. ## Upstream license notice MIT License Copyright (c) 2025 Petr Král Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Dave AI resource metadata Creator / publisher: pekral Original project: https://github.com/pekral/cursor-rules/blob/24214b75cd351b83609811ec39b25925582c7aa3/skills/auto-fix-bug/SKILL.md Attribution basis: Recovered original package and original project license at a pinned revision Fields of work: Development & Engineering, Product Management, Customer Support Roles: Backend Developer, DevOps / SRE, Product Manager, QA / Test Engineer, Technical Support Specialties: Backend, Git Tools: GitHub Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: e6cdaf2da60c8512d24ebd349ed14109ce593f7cd3d9ea41cb52f8293444fd31 Metadata reviewed: 2026-10-27 This metadata supersedes earlier Dave AI catalog attribution. Original instruction and supporting files are preserved.