Create PR
PR best practices checklist — merge master, validate, link tasks, test coverage, structure for review
- What
- PR best practices checklist — merge master, validate, link tasks, test coverage, structure for review
- Cost
- Free
- Needs
- an AI agent harness (Claude Code, Codex, Pi, Antigravity, Hermes, or Muse); a git repo and the gh CLI if you want to open the PR directly
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the pre-PR checklist, actionable. Honest labeling: written for the Warp repo (merge origin/master, link Linear tasks, reference the Warp integration workflow) — the conventions are Warp's, but the checklist transfers: merge master into your branch first and resolve conflicts locally, review your own changes (log, diff stat, full diff) before submitting, validate efficiently, link tasks (Linear), ensure appropriate test coverage, structure the PR for effective review. Complementary to warpdotdev-review-pr (this lot): this one creates PRs, the other reviews them. References sibling skills not yet indexed (write-pr-description, fix-errors, warp-integration-test, add-feature-flag) — future candidates. By @warpdotdev, listed here with credit to its creator. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: an AI agent harness (Claude Code, Codex, Pi, Antigravity, Hermes, or Muse); a git repo and the gh CLI if you want to open the PR directly Install "Create PR" for me. PR best practices checklist — merge master, validate, link tasks, test coverage, structure for review Repository: https://github.com/warpdotdev/common-skills/blob/main/.agents/skills/create-pr/SKILL.md 1. Fetch the SKILL.md file for the warpdotdev-create-pr skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "warpdotdev-create-pr". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.