create-pr

[!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

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

Step 2: Create the changeset

1. 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: