Menu
Create a well-formed draft PR for ts-libs. Covers changeset, commit check, PR body, and gh CLI invocation.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/LedgerHQ/ts-libs --skill github-prThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Import a single library from ledger-live into this ts-libs monorepo. Runs discovery, dep/PR audit, copies files, patches config, and verifies the build. Source repo: https://github.com/LedgerHQ/ledger-live
Format a conventional commit message for ts-libs. Use when writing or reviewing a commit message.
Create a changeset for modified packages in ts-libs. Use when preparing a PR or documenting package changes for release.
Based on SOC occupation classification
Showing SKILL.md
| name | github-pr |
| description | Create a well-formed draft PR for ts-libs. Covers changeset, commit check, PR body, and gh CLI invocation. |
| disable-model-invocation | true |
/git-workflow — verify branch name and commit formatgit diff develop..HEAD --stat — confirm scope of changes/create-changeset — add a changeset if any libs/* package changed### ✅ Checklist
- [x] Changeset attached (`pnpm changelog`)
- [{{TEST_CHECKBOX}}] Covered by automatic tests{{TEST_NOTE}}
- [x] Impact: {{IMPACT}}
### 📝 Description
{{DESCRIPTION}}
### ❓ Context
{{CONTEXT}}
---
### 🧐 For Reviewers
- Code aligns with requirements described in context
- No undocumented trade-offs or technical debt introduced
- Tests cover the meaningful cases
- Public API changes are intentional and backward-compatible (or breaking change documented)
TEST_CHECKBOX: x if tests exist, if not (explain why in TEST_NOTE)IMPACT: one-line description of what could regressDESCRIPTION: problem → solution, include code examples for API changesCONTEXT: Jira/GitHub link or plain descriptiongit push -u origin HEAD
gh pr create --draft \
--base develop \
--title "<type>(<scope>): <description>" \
--body "$(cat <<'EOF'
<generated body>
EOF
)"
Always use --draft. Always target develop.