create-fix-pr
Investigates a root cause and files a minimal fix PR for a reported bug or observability finding.
- Installs
- 662
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/launchdarkly/ai-tooling --skill create-fix-pr- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads create-fix-pr automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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.
FAQ
What does the create-fix-pr skill do?
Investigates a root cause and files a minimal fix PR for a reported bug or observability finding.
How do I install create-fix-pr?
Run npx skills add https://github.com/launchdarkly/ai-tooling --skill create-fix-pr in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/create-fix-pr/ (personal) or .claude/skills/create-fix-pr/ (project).
Which AI agents can use create-fix-pr?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is create-fix-pr safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains create-fix-pr?
It is published by launchdarkly in launchdarkly/ai-tooling. It has 662 recorded installs.
More from launchdarkly/ai-tooling
onboarding
launchdarkly/ai-tooling
Scripted onboarding for LaunchDarkly: quiet execution, fixed sequence, SDK install, first flag with a live reveal, MCP offered afterwards. Enforces step completion before advancing and redirects drift. Use when adding LaunchDarkly, setting up or integrating feature flags in a project, SDK integration, or 'onboard me'.
launchdarkly-flag-discovery
launchdarkly/ai-tooling
Audit your LaunchDarkly feature flags to understand the landscape, find stale or launched flags, and assess removal readiness. Use when the user asks about flag debt, stale flags, cleanup candidates, flag health, or wants to understand their flag inventory.
launchdarkly-flag-create
launchdarkly/ai-tooling
Create and configure LaunchDarkly feature flags in a way that fits the existing codebase. Use when the user wants to create a new flag, wrap code in a flag, add a feature toggle, or set up an experiment. Guides exploration of existing patterns before creating.
launchdarkly-flag-targeting
launchdarkly/ai-tooling
Control LaunchDarkly feature flag targeting including toggling flags on/off, percentage rollouts, targeting rules, individual targets, and copying flag configurations between environments. Use when the user wants to change who sees a flag, roll out to a percentage, add targeting rules, or promote config between environments.
launchdarkly-flag-cleanup
launchdarkly/ai-tooling
Safely remove a feature flag from code while preserving production behavior. Use when the user wants to remove a flag from code, delete flag references, or create a PR that hardcodes the winning variation after a rollout is complete.
launchdarkly-metric-choose
launchdarkly/ai-tooling
Choose the right metrics for a LaunchDarkly experiment, guarded rollout, or release policy. Use when the user wants to know which metrics to use, which is the primary metric for an experiment, what guardrails to add, or which events to monitor in a rollout. Surfaces what will auto-attach from existing release policies before making additional recommendations.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.