How do I install the Opening Pr skill?

Run npx skillmds@latest add socketdev/opening-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 Opening Pr skill do?

Implement a requested change, verify it, commit it, and open or update the PR. It is listed under Coding & Dev Tools on SkillMD.

Is Opening Pr safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Opening 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 Opening Pr free to use?

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

Who published Opening Pr?

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

Opening Pr by socketdev — Agent Skill

Name: Opening Pr
Author: socketdev

File contents

opening-pr

Ship a change as a PR that actually fixes the thing AND proves it — a PR without a test or a named verification path is not done. The sibling of decomposing-tickets: that one writes the work down, this one lands it.

1. Understand the target

Read the issue / finding / request and the affected code. If it's a findings report, this is the fix agent's job — deterministic fixers first, AI-patch the residue. If it's a feature or bug, drive it test-first with building-tdd.

2. Fix it

Apply the change. Deterministic fixers (pnpm run fix / format / the finding's named script) run before any hand patch (code-first-then-ai). Smallest change that resolves the target; don't refactor unrelated code.

3. Verify — the non-negotiable step

The change MUST carry one of:

A unit/integration test at the correct seam that goes red without the fix and green with it (the default — drive it via building-tdd; seam doctrine: test-layout), OR
A named verification path when a test genuinely can't reach it (a pnpm command, a check script, a reproducible manual step) — stated explicitly in the PR body, never "trust me".

Run pnpm run check + pnpm test <file> and confirm green. No green verification, no PR.

4. Write the PR body through prose + doctrine

Run the prose skill over the PR description (conversational mode) and apply prose-style-and-doctrine: lead with what changed and why, 1–3 sentences, no throat-clearers, no diff narration, evidence, the test/command that proves it. Public-surface hygiene: no real customer/company name, no private repo, no Linear ref, no bare #N (use org/repo#N or the full URL); link the issue with a closing keyword.

5. Open it

Commit on a branch — a worktree if the primary checkout has other sessions — push, gh pr create. Opening a PR is outward-facing — confirm the base branch + that the diff is the intended scope first.

Completion criterion

The fix is applied, pnpm run check + the test/verification are green, the PR body has passed the prose + doctrine pass and leaks no private name, and the PR links its issue. A PR with no test and no named verification path is not complete.

Handoffs

Use prose for the outward-facing body and pushing for the full pre-push and CI-green loop.

---name: opening-prdescription: Implement a requested change, verify it, commit it, and open or update the PR.---# opening-prShip a change as a PR that actually **fixes the thing** AND **proves it** — a PRwithout a test or a named verification path is not done. The sibling of`decomposing-tickets`: that one writes the work down, this one lands it.## 1. Understand the targetRead the issue / finding / request and the affected code. If it's a findingsreport, this is the `fix` agent's job — deterministic fixers first, AI-patch theresidue. If it's a feature or bug, drive it test-first with `building-tdd`.## 2. Fix itApply the change. Deterministic fixers (`pnpm run fix` / `format` / the finding'snamed script) run before any hand patch ([`code-first-then-ai`](../../../rules/fleet/code-first-then-ai.md)).Smallest change that resolves the target; don't refactor unrelated code.## 3. Verify — the non-negotiable stepThe change MUST carry one of:- A **unit/integration test** at the correct seam that goes red without the fix and green with it (the default — drive it via `building-tdd`; seam doctrine: [`test-layout`](../../../../docs/agents.md/fleet/test-layout.md)), OR- A **named verification path** when a test genuinely can't reach it (a `pnpm` command, a check script, a reproducible manual step) — stated explicitly in the PR body, never "trust me".Run `pnpm run check` + `pnpm test <file>` and confirm green. No green verification,no PR.## 4. Write the PR body through prose + doctrineRun the `prose` skill over the PR description (conversational mode) and apply[`prose-style-and-doctrine`](../../../rules/fleet/prose-style-and-doctrine.md):lead with what changed and why, 1–3 sentences, no throat-clearers, no diffnarration, evidence, the test/command that proves it. Public-surface hygiene: noreal customer/company name, no private repo, no Linear ref, no bare `#N` (use`org/repo#N` or the full URL); link the issue with a closing keyword.## 5. Open itCommit on a branch — a worktree if the primary checkout has other sessions — push,`gh pr create`. Opening a PR is outward-facing — confirm the base branch + thatthe diff is the intended scope first.## Completion criterionThe fix is applied, `pnpm run check` + the test/verification are green, the PR bodyhas passed the prose + doctrine pass and leaks no private name, and the PR linksits issue. A PR with no test and no named verification path is not complete.## HandoffsUse [prose](../prose/SKILL.md) for the outward-facing body and[pushing](../pushing/SKILL.md) for the full pre-push and CI-green loop.

Frequently asked questions

Opening Pr