How do I install the Jmerta Codex Skills Create Pr skill?

Run npx skillmds@latest add tomevault-io/jmerta-codex-skills-create-pr in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Jmerta Codex Skills Create Pr skill do?

Create a PR It is listed under Coding & Dev Tools on SkillMD.

Is Jmerta Codex Skills Create Pr safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Jmerta Codex Skills Create Pr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Jmerta Codex Skills Create Pr free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Jmerta Codex Skills Create Pr?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Jmerta Codex Skills Create Pr by tomevault-io

Name: Jmerta Codex Skills Create Pr
Author: tomevault-io

File contents

Create a PR

Goal

Produce a PR that’s easy to review and safe to merge:

small, scoped changes
green checks (lint/tests/build as appropriate)
clear description + validation steps

Workflow (checklist)

Confirm scope
- Restate the goal and acceptance criteria.
- Identify files likely to change; avoid unrelated cleanup.
Create a branch
- Use a descriptive name: fix/<topic>, feat/<topic>, chore/<topic>.
Implement changes
- Keep diffs focused; prefer small commits.
Run quality gates
- Run the repo’s standard commands (lint/tests/build).
- If bun.lock exists, prefer bun lint / bun build.
- If bun.lock exists but bun is not available, tell the user and ask whether to install bun or use the repo’s alternative package manager.
Commit
- Prefer Conventional Commits: fix: ..., feat: ..., chore: ....
Push + open PR
- Always use GitHub CLI (gh) for PR workflows (e.g. gh pr create --fill).
- If gh is not authenticated, run gh auth login (or gh auth status to check).
- If gh is not installed or cannot be authenticated, tell the user and ask whether to install/authenticate or proceed with manual PR creation steps.
Fill in PR body
- Use references/pr-description-template.md.

Notes

Don't force-push unless you're sure it's safe for collaborators.
If the PR changes UX, include screenshots or a short GIF.
Prefer gh for create/view/checks (e.g. gh pr view, gh pr checks).

Deliverable

Provide:

Branch name and PR URL (or the exact steps to open it manually).
PR title/body (using references/pr-description-template.md).
Commits included and verification commands run.
Screenshots/GIFs if UX changed.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: jmerta-codex-skills-create-prdescription: Create a PR---# Create a PR## GoalProduce a PR that’s easy to review and safe to merge:- small, scoped changes- green checks (lint/tests/build as appropriate)- clear description + validation steps## Workflow (checklist)1) Confirm scope - Restate the goal and acceptance criteria. - Identify files likely to change; avoid unrelated cleanup.2) Create a branch - Use a descriptive name: `fix/<topic>`, `feat/<topic>`, `chore/<topic>`.3) Implement changes - Keep diffs focused; prefer small commits.4) Run quality gates - Run the repo’s standard commands (lint/tests/build). - If `bun.lock` exists, prefer `bun lint` / `bun build`. - If `bun.lock` exists but `bun` is not available, tell the user and ask whether to install `bun` or use the repo’s alternative package manager.5) Commit - Prefer Conventional Commits: `fix: ...`, `feat: ...`, `chore: ...`.6) Push + open PR - Always use GitHub CLI (`gh`) for PR workflows (e.g. `gh pr create --fill`). - If `gh` is not authenticated, run `gh auth login` (or `gh auth status` to check). - If `gh` is not installed or cannot be authenticated, tell the user and ask whether to install/authenticate or proceed with manual PR creation steps.7) Fill in PR body - Use `references/pr-description-template.md`.## Notes- Don't force-push unless you're sure it's safe for collaborators.- If the PR changes UX, include screenshots or a short GIF.- Prefer `gh` for create/view/checks (e.g. `gh pr view`, `gh pr checks`).## DeliverableProvide:- Branch name and PR URL (or the exact steps to open it manually).- PR title/body (using `references/pr-description-template.md`).- Commits included and verification commands run.- Screenshots/GIFs if UX changed.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/jmerta) — claim your Tome and manage your conversions.

Frequently asked questions

Jmerta Codex Skills Create Pr