How do I install the Create Fix Pr skill?

Run npx skillmds@latest add launchdarkly/create-fix-pr in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Create Fix Pr safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Create Fix Pr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Create Fix Pr free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Create Fix Pr?

launchdarkly (@launchdarkly) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Create Fix Pr by launchdarkly — Agent Skill

Name: Create Fix Pr
Rating: 4.2 (5 reviews)
Author: launchdarkly

File contents

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 investigate skill 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.md or CLAUDE.md at 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.md for 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-review skill'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.

---name: create-fix-prdescription: Investigates a root cause and files a minimal fix PR for a reported bug or observability finding.license: Apache-2.0--- # 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 1. **Investigate.** Use the `investigate` skill to find the root cause. Cite the exact trace ID, log line, error group, and code location that pins the problem. 2. **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. 3. **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. 4. **Get the repo.** Clone it if you don't already have it locally — `gh repo clone <owner>/<repo>`. 5. **Check for repo conventions.** Read `agents.md` or `CLAUDE.md` at the repo root — these describe repo-specific rules your fix needs to respect. 6. **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. 7. **Set git identity** before committing — see `pr-conventions.md`. 8. **Commit, push, and file the PR.** See `pr-conventions.md` for 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-review` skill'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.

Frequently asked questions

Create Fix Pr