Index of every page on this site: llms.txt
All skills
launchdarkly avatar

/create-fix-pr

@f0ee110 official
Run it yourself

Investigates a root cause and files a minimal fix PR for a reported bug or observability finding.

Use this Skill: https://skilld.dev/gh/launchdarkly/ai-tooling/create-fix-pr

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈28 tokens for metadata: the name and description. ≈617 when used: this file. ≈737 more on demand in 1 file.

Description uses 1.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈113 characters, or 1.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts4mo3 checks · Risk SAFE
  • Gen Agent Trust Hub4mo

    The skill automates the investigation and fixing of bugs by creating pull requests. While it includes explicit instructions to avoid committing secrets or credentials, it is vulnerable to indirect prompt injection as it is instructed to follow rules defined in untrusted files within external repositories.

  • Socket4mo

    No alerts

  • Snyk4mo

    Risk: LOW · No issues

Signed by skilld at f0ee110. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 5 months ago
compatibility
Requires git and the GitHub CLI (gh); pairs with the investigate skill
metadata
{
  "author": "launchdarkly",
  "version": "0.1.0"
}

README badge

README badge for launchdarkly/ai-tooling/create-fix-pr