prathamdby/skills

make-pr

make-pr when publishing committed branch changes as a new pull request or updating the existing pull request for that branch.

First seen May 31, 2026

Installation

$ npx skills add prathamdby/skills --skill make-pr

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from prathamdby/skills · top by installs.

npx skills add prathamdby/skills

Browse all from prathamdby/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 4
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,316 B
  • docs SUMMARY.md 1,012 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 381 installs

SKILL.md

Make PR

Flags

Flag Default Effect
--target <branch> main PR base and branch-diff target
--ticket <id> off Prefix title with [<id>]
--conventional off Use conventional title rules

Missing flag values are BLOCKED. Never infer a ticket from branch names, commits, issues, or conversation.

1. Preflight

Resolve current branch, target ref, working-tree status, upstream state, and an open PR for the branch; ignore closed PRs and block if several are open. Resolve the push remote from configured upstream, otherwise origin, and fetch it before comparing. Block on detached HEAD, current branch equal to target, missing target, fetch failure, behind or diverged upstream, any uncommitted or untracked file, or an open PR whose base differs from target.

Record: branch/target | diff hash | remote state | open PR | title/body/tier | mutation | terminal.

Done when the branch is clean, the base is fixed, and create versus update is known.

2. Lock diff and write copy

Read git diff <target>...HEAD only and hash it with git hash-object --stdin. If empty, report NO_CHANGES. Draft as a stranger who has only this diff and the explicit ticket ID.

  • Default title: imperative sentence case, no type prefix, no trailing period,

summary at most 60 characters.

  • Conventional title: load its section and shared rejection check from

../commit/REFERENCE.md; keep the 50-character subject limit. Only an explicit ticket prefix is exempt from the ticket-ID rejection.

  • Ticket: prepend [<id>] exactly as supplied; the prefix does not authorize

ticket claims in the body and does not count toward the subject limit.

  • Body: measure the locked diff, pick the tier, and draft per Body scale and

Body style in ./REFERENCE.md. For every tier, including S, add Body visuals for every theme with a proved shape. Classify that shape against Pick the views in ./REFERENCE.md and place each view next to its theme. Group related hunks, never commits. Include no test, rollout, motive, ticket claim the diff cannot prove, or harness footer.

Map every title phrase, body line, and visual label to proving paths and hunks. Rewrite untraced copy. Done when format, chosen tier, Body style, Body visuals, and clean-room trace pass.

3. Publish

Recheck status and diff hash. If either changed, return to Step 1. Publish the committed branch to the resolved remote with a normal upstream push when missing or ahead. Never force push. After fetch, local HEAD and upstream must match before PR mutation. Block on ambiguity or push failure.

Create a PR when none exists. Otherwise update the existing title and body while changing no other field; preserve draft state, reviewers, labels, assignees, linked issues, and projects. Use target and current branch explicitly. Record mutation as none, pushed, pr-created, or pr-updated after each successful action.

Done when the platform returns a PR URL or a captured mutation error.

4. Verify and report

Read the PR back. Verify URL, base, head, title, body, and preserved draft state against the ledger. On a partial API result or non-body field mismatch, retry the PR mutation once after read-back; then report BLOCKED with a field-level difference. Auth, rate-limit, fetch, push, and platform errors are also BLOCKED.

Then apply Body hygiene in ./REFERENCE.md: the body must equal the ledger body (single trailing newline only). If harness footers or other text were appended, update the body once to the exact ledger body, re-read, and report whether a strip ran. Still dirty is BLOCKED.

Report create or update, push status, URL, body strip status, chosen tier, and trace summary only after read-back matches.

After interruption, re-run Preflight and verify remote and PR state before any retry. Do not duplicate a PR or repeat a successful push.

Terminal values are SUCCESS, NO_CHANGES, and BLOCKED. Never commit, force push, reopen a PR, run builds, or run tests.