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

/should-auto-approve

@f0ee110 official
Run it yourself

Rates a committed code change's review risk as low, medium or high by a fixed decision graph (low can be approved without a human; medium and high need one), from checked answers to narrow questions about the change. Use only when your instructions or the user name should-auto-approve. Advisory and read-only: it never approves, comments on, or changes a pull request.

Use this Skill: https://skilld.dev/gh/launchdarkly/ai-tooling/should-auto-approve

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

README.md

≈428 tokens on demand. Your agent reads this file only when SKILL.md points to it.

should-auto-approve

Rates a committed code change's review risk as low (can merge on an automated approval), medium or high (needs a person). A fixed decision graph asks narrow yes/no questions about the change: the changed paths answer some, the agent answers the rest by written procedures from the code, and the graph turns the answers into the rating. The same answers always give the same rating.

  • Advisory and read-only. It never approves, comments on or changes a pull request, never changes a flag, and never edits the repository it checks.
  • Needs a git checkout with the change committed and its merge base, python3 (3.10+, standard library only) and git.
  • Output: a short report ending in a should-auto-approve JSON block (rating, terminal, steps, values, graph, and the approval gates with auto_approve).
  • Shadow mode: told to run in shadow mode, the agent prints the report and does nothing else with it.

Command line

should-auto-approve.pyz is the whole program in one file (a Python zip application: the walk, the graph and its questions). start, flag, answer, decide; python3 should-auto-approve.pyz --help lists them. SKILL.md gives the order, and references/QUESTIONS.md every question.

Settings

Variable Default What it sets
LAUNCHDARKLY_BASE_URI https://app.launchdarkly.com The LaunchDarkly instance.
LAUNCHDARKLY_PROJECT default The project whose flags the change may name.
SHOULD_AUTO_APPROVE_RUNS ~/.cache/should-auto-approve/ Where run folders go.

Built from the risk graph at version 0.12 (graph e6cc6fe7a229).

Source: SKILL.md on GitHub

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.

2 warnings1d3 checks · Risk SAFE
  • Gen Agent Trust Hub1d

    This skill provides a read-only advisory tool from LaunchDarkly to evaluate code change risk. It includes robust instructions to mitigate indirect prompt injection from the code being reviewed.

  • Socket1d

    1 alert: gptSecurity

  • Snyk1d

    Risk: MEDIUM · 1 issue

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 2 days ago
metadata
{
  "author": "launchdarkly",
  "version": "0.7.1",
  "graph": "e6cc6fe7a229"
}
Other metadata
compatibility
Advisory and read-only. Needs a git checkout with the change committed and its merge base present, a shell, git and Python 3.10+ (no packages). Reads LaunchDarkly flag state through your LaunchDarkly tools. Ends with a `should-auto-approve` JSON block.

README badge

README badge for launchdarkly/ai-tooling/should-auto-approve