agentleFS
SamuelBostic29SamuelBostic29/claude-skills/skills/draft-pr/SKILL.md

draft-pr

Skill1 starsChanged 4 months agoMITView on GitHub

Finish a unit of work into a draft PR: stage only the files changed in this session, commit, push, write a description from a configurable template, and open it as a draft. Use when asked to draft/open a PR or write up changes for review after finishing work on a branch.

  • Reads credentials
  • Commits and pushes

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use interview and frontend-design.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dazuckSkill

    interview

    Interview me about a plan to flesh out requirements before implementation. Asks non-obvious questions one at a time until all ambiguities are resolved.

    Also in 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    NEVER: use git add -A, git add ., git add -u, or git commit -a.

    line 46
  2. Distinctive:

    Run git status --short and compare.

    line 47
  3. Distinctive:

    If you're unsure whether a file belongs to this session's changeset, exclude it and say so — under-staging is safe, over-staging can leak.

    line 49
  4. Very specific:

    Read the branch name and extract a ticket/issue number from common patterns — e.g.

    line 95
  5. Very specific:

    If the host is GitHub and the number is a repo issue, emit Closes #<n>.

    line 96
  6. Distinctive:

    If you can't confidently derive a number, ask the user or omit the line — don't guess.

    line 98
  7. Distinctive:

    Branch off the default branch: before committing — never commit onto main/master.

    line 105
  8. Distinctive:

    A few clear sentences per section: No filler, no restating the ticket verbatim.

    line 107

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Draft PR: stage the session's work, commit, push, and open a draft PR

You are wrapping up a unit of work into a pull request. Your job is to commit and push only the files you changed during this working session, write a clean description from the template below, and open the PR as a draft. You open drafts only — never mark ready, never merge.

The single most important rule of this skill is safe staging (see below). The user routinely has other locally-modified files — app-specific setup, local config, files containing secrets — that must never be committed. You stage by explicit path, only the files this session touched, and nothing else.

When to use this skill

  • "Draft a PR" / "open a draft PR" / "make a PR for what I just did"
  • "Write up these changes for review" after finishing work on a branch

When NOT to use this skill

  • Marking a PR ready for review, or merging — this skill stops at draft.
  • Reviewing someone else's PR.
  • Committing without a PR, or committing files you didn't change this session.

Safe staging (read first — this is the cardinal rule)

  • Stage only the files YOU created or edited during this session, listed by explicit path. You know this set from your own edits this session.
  • NEVER use git add -A, git add ., git add -u, or git commit -a. No blanket staging, ever.
  • Run git status --short and compare. Any modified/untracked file you did NOT touch this session is excluded — do not stage it. These often hold secrets or local-only setup. Report them as left-untouched; never commit them.
  • Even among files you touched, never stage obvious secret/local-config files (.env, *.local.*, *.pem, *.key, credential or appsettings.* files). If the work genuinely required changing one, stop and ask instead of staging it.
  • If you're unsure whether a file belongs to this session's changeset, exclude it and say so — under-staging is safe, over-staging can leak.

Steps

  1. Build the changeset. List the exact files you created or edited this session. Run git status --short to see everything dirty, and split it into this-session (will stage) vs other (will not touch).
  2. Pick the branch. Get the current branch (git branch --show-current). If it's the default branch (main/master), create a feature branch first (git checkout -b <name>) — derive a short kebab-case name from the work or ticket. Never commit the changeset directly onto the default branch.
  3. Stage explicitly. git add <path1> <path2> … with the this-session paths only. Confirm with git status --short that nothing else got staged.
  4. Commit. Write a descriptive message — an action-led subject line, plus (for non-trivial work) a short body of bullets covering what changed and why. This message is the primary source for the PR's What Changed section, so make it accurate and complete. No Co-Authored-By / AI attribution. Match the existing repo commit style if evident.
  5. Push. git push -u origin <branch>.
  6. Report the changeset. Tell the user exactly what was committed and what was deliberately left unstaged:
    Committed & pushed (N files): <paths>
    Left untouched (not part of this session): <paths or "none">
  7. Draft the description. Build What Changed primarily from the commit message(s) on this branch (git log <base>..HEAD), reconciled against git diff so nothing is misstated or missed. Get the repo name (gh repo view --json name --jq .name), derive the issue link (see Issue linking), and ask the verification/testing type via AskUserQuestion (API · UI · data-migration · infra · none). For the testing-section formats, read references/testing-variants.md once the variant is known. Build the description from Output format.
  8. Open as a draft. gh pr create --draft --base <base> --head <branch> --title "<title>" --body-file <file>. Always --draft. Report the PR URL and stop.

Output format

The template is configurable; this is the default. Omit any section that doesn't apply.

<issue-link line — see Issue linking; omit if none>

## What Changed

- <Action-led bullet — "Added…", "Switched…", "Removed…" — with the why when non-obvious>

## Review Focus

- <Where reviewers should look; dependencies on other PRs; auth/perf/edge-case concerns>

## Testing

<The variant chosen in step 7, formatted per references/testing-variants.md. Omit if "none".>

Issue linking (tracker-agnostic)

  1. Read the branch name and extract a ticket/issue number from common patterns — e.g. feature/PROJ-123-..., 123-short-desc, gh-123, <base>_<TICKET>-<n>.
  2. If the host is GitHub and the number is a repo issue, emit Closes #<n>.
  3. For any other tracker, build the link from a configurable base URL the adopter sets — placeholder <TRACKER_URL_BASE> — e.g. [Ticket](<TRACKER_URL_BASE>/<n>). Never hardcode a tracker host, workspace ID, or org.
  4. If you can't confidently derive a number, ask the user or omit the line — don't guess.

Rules

What to do

  • Safe staging above all. Explicit paths only; report what you excluded.
  • Branch off the default branch before committing — never commit onto main/master.
  • Lead bullets with the action verb; include motivation when it isn't obvious.
  • A few clear sentences per section. No filler, no restating the ticket verbatim.
  • Ask the verification type before drafting, so the Testing section is right the first time.

What NOT to do

  • NEVER blanket-stage (git add -A/./-u, commit -a) or stage a file you didn't change this session.
  • NEVER stage secret/local-config files — stop and ask if the work touched one.
  • NEVER mark the PR ready or merge it. Draft only.
  • NEVER add Co-Authored-By or AI-attribution lines to commits or the PR body.
  • No hardcoded org, team label, tracker URL/workspace, or real-world examples. Everything project-specific is a <PLACEHOLDER>.

Format discipline

  • Report the changeset (committed vs left-untouched) plainly, then the PR URL. No preamble.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.