A manual workflow for creating a pull request, the review request used to propose code changes, with its required title, description, changeset, and testing details.

Use it to prepare pull requests from an issue, describe the change type and scope, report test coverage, identify QA areas, and include screenshots for interface changes.

It helps turn completed work into a reviewable pull request with the information maintainers and testers need.

How LedgerHQ/ledger-live configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to LedgerHQ/ledger-live. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/LedgerHQ/ledger-live/develop/.agents/skills/create-pr/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/LedgerHQ/ledger-live

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ledgerhq/ledger-live/create-pr/github.svg)](https://agentmods.dev/skills/ledgerhq/ledger-live/create-pr)

Your own site

<a href="https://agentmods.dev/skills/ledgerhq/ledger-live/create-pr"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/create-pr/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ledgerhq/ledger-live/create-pr"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/create-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,218 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium Agent Snooping · line 100
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.

Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00055	$0.01218
Opus 5.5	$0.00022	$0.00487
Sonnet 5.5	$0.00011	$0.00244
Haiku 4.5	$0.00006	$0.00122

Measured yesterday against content hash f8a1b6b785ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/create-pr/SKILL.md · 160 lines

How it starts

The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.

[!TIP]

Note: this skill is for manual, user-invocation only. Agents should only read this only when it is specifically invoked. Canonical Git conventions take precedence over this command.

Create PR

Create a pull request with a valid title, description, changeset, and all required elements.

Prompt Variables

$TICKET_URL

Paste the JIRA or GitHub issue URL (e.g., https://ledgerhq.atlassian.net/browse/LIVE-1234)

$TICKET_DESCRIPTION

Describe the ticket context: What is the problem? What should be done? Include acceptance criteria if available.

$CHANGE_TYPE

Select the type of change: feat | fix | refactor | test | docs | chore

$CHANGE_SCOPE

Summarise the scope in a single term? (e.g. architecture, coin-evm, counter-values, e2e, portfolio, swap)

$TEST_COVERAGE

Are changes covered by tests? yes | no | partial - If not fully covered, explain why.

$QA_FOCUS_AREAS

What specific areas should QA focus on when testing this PR?

$HAS_UI_CHANGES

Are there visual/UI changes? yes | no - If yes, you will need to edit the PR description to add screenshots.

Instructions

Step 1: Analyze the changes

Follow docs/contributing/git-conventions.md for valid commit messages
Run git status and git diff to understand current changes
Run git log develop..HEAD --oneline to see commits on this branch
Identify all modified packages for the changeset

Step 2: Create the changeset

Use the create-changeset skill to add a changeset for the modified packages.

Step 3: Prepare the PR

Generate the PR body using .github/pull_request_template.md.

Step 4: Create the Pull Request

First, push the branch:

git push -u origin HEAD

Then create the PR as draft and capture the URL:

PR_URL=$(gh pr create --draft --title "{{PR_TITLE}}" --body "$(cat <<'EOF'
{{GENERATED_PR_BODY}}
EOF
)")

Then open the PR in the browser:

Read the full file on GitHub · 160 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday Changed · +34 tokens per session f8a1b6b785ab
2mo ago First seen · 160 lines · 21 tokens per session scan A ce80315cc837

Subscribe to this mod's changes

create-pr is a skill published in the GitHub repository LedgerHQ/ledger-live (624 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 1,218 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflow ledger-live ledger-wallet renovate-operator

merge-batch

Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.

diegosouzapw/OmniRoute · 46 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

release-helper

Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.

Sahir619/fable-method · 43 tokens

merge-pr

Merge a pull request with status checks, squash merge, and branch cleanup. Handles worktree contexts.

joshukraine/dotfiles · 23 tokens

changelog-composer

Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".

Mathews-Tom/armory · 67 tokens

ledger-live: Skill for Claude Code