Finds the root cause of a reported bug or observability finding, then opens a pull request with the smallest fix that solves it. It looks for an existing open pull request first, and describes the fix instead when it needs a config change or a flag flip.
WHEN YOUR AGENT SHOULD USE IT
USE FOR
- Turn an investigated bug into a pull request ready for review.
- Avoid a duplicate pull request when someone is already fixing the issue.
- Keep fixes small: no refactors, extra features or unrelated bug fixes.
DO NOT USE FOR
- Fixes that need a config change, a flag flip or code you can't reach: it writes up the solution instead.
This is the playbook your agent receives when the skill activates — you don't need to read it to use the skill, but it's here to audit before installing.
Create a fix PR
Overview
You are investigating a problem and filing a pull request that resolves it. This builds on the investigate skill — do the investigation properly first, don't jump to a fix without evidence.
Use the gh CLI for all GitHub operations (auth comes from your gh login) and standard Bash / Edit / Read / Grep for everything else.
Workflow
- Investigate. Use the
investigateskill to find the root cause. Cite the exact trace ID, log line, error group, and code location that pins the problem. - Confirm there isn't already a PR open. Before filing anything, search GitHub for an existing open PR addressing the same issue —
gh pr list --search "<keywords>" --state open. If one exists, direct the user to it — do not create a duplicate. - Judge whether a PR is the right tool. If the fix requires a config change, a flag flip, or a change outside the code you can access, describe the solution instead of filing a PR.
- Get the repo. Clone it if you don't already have it locally —
gh repo clone <owner>/<repo>. - Check for repo conventions. Read
agents.mdorCLAUDE.mdat the repo root — these describe repo-specific rules your fix needs to respect. - Make the change. Minimal diff. Don't refactor surrounding code, don't add features, don't fix unrelated bugs you happen to notice. One PR, one fix.
- Set git identity before committing — see
pr-conventions.md. - Commit, push, and file the PR. See
pr-conventions.mdfor branch naming and PR body rules.
What's a good fix
- Changes the smallest possible number of lines
- Preserves current production behavior unless the bug IS the current behavior
- Doesn't depend on assumptions you can't verify from the evidence
- Would pass a
code-reviewskill's check if one existed
What isn't
- Sweeping refactors unrelated to the reported problem
- Speculative null checks or error handling added "while you're in there"
- Changes to tests that hide the underlying bug
- Bumping dependency versions to fix a symptom
Restricted tools
If gh isn't installed or gh auth status shows no auth, surface the error to the user and stop — don't try alternative auth schemes.
Never include in a PR
- GitHub access tokens or any other secrets or credentials.
- Debugging logs or print statements you added during investigation.
Follow the repo's own commit and PR conventions for everything else.
Needs another service connected
2 FOR YOUYou need all of these
- 01Git and the GitHub CLI, signed in
Git and the GitHub CLI (gh), signed in with your gh login. If gh is missing or not signed in, the skill stops and tells you.
- 02LaunchDarkly's investigate skill as well
Install LaunchDarkly's investigate skill too: this skill runs it first to find the cause. Investigate needs LaunchDarkly's hosted MCP server, which LaunchDarkly's plugin for Claude Code adds.
In the launchdarkly/ai-tooling repository — the LaunchDarkly Agent Skills plugindoesn't install this skill.
Copy & paste — that's it
npx skills add launchdarkly/ai-tooling --skill "create-fix-pr" --full-depthRun this in your project — your agent picks the skill up automatically.
Licensed under Apache-2.0— you can use, modify, and redistribute it under that license's terms.
View the full license file on GitHub →