agentleFS
farhan0167farhan0167/cv-claw/.claude/skills/pr-message/SKILL.md

pr-message

Skill4 starsChanged 6 months agoMITView on GitHub

Draft a pull-request message (title + Markdown body) for the current branch into main. Use when the user asks for a "PR message", "PR description", "pull request message", or says "write a PR message" / "give me a PR message". Output is Markdown text only — does not call `gh` or open a PR.

  • Commits and pushes

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. milistu/agent-skills★ 8same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Discover scope: Run these in parallel and read the results:

    line 27
  2. Distinctive:

    Sanity-check the state: Stop and tell the user (don't draft) when any of these hold:

    line 37
  3. Distinctive:

    Decide whether to ask for framing: Ask the user *before* drafting only when:

    line 45
  4. Very specific:

    Prefer the dominant conventional-commit prefix from the branch (feat:, fix:, refactor:, docs:, chore:).

    line 58
  5. Distinctive:

    Three sections only: No Notes / Open questions / Followups section.

    line 138
  6. Distinctive:

    Don't fabricate test steps: If a verification step isn't real (no test suite exists, no CI workflow exists), don't list it.

    line 140
  7. Distinctive:

    User asks while on main: Stop; ask which branch they meant.

    line 166
  8. Distinctive:

    Detached HEAD: Stop; ask the user to check out a branch first.

    line 167

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

pr-message

Draft a PR message for merging the current branch into main and hand the user a single fenced Markdown block they can paste into the GitHub UI or into gh pr create --body-file -.

This skill is repo-local to py-cv-claw. It does not call gh and does not open or edit PRs.

Defaults

  • base = main
  • head = the current branch (typically dev; whatever git rev-parse --abbrev-ref HEAD returns)

Print what you inferred at the top of your reply. Do not ask the user to confirm base/head unless head is main itself (in which case stop and ask — there's nothing to merge).

Procedure

  1. Discover scope. Run these in parallel and read the results:
    • git rev-parse --abbrev-ref HEAD — confirm head branch.
    • git log --oneline main..HEAD — commits on the branch.
    • git diff main...HEAD --stat — file-level shape (note the triple-dot: changes on HEAD relative to the merge base, ignoring work added to main since the branch diverged).
    • git diff main...HEAD — read enough of the actual diff to verify commit messages tell the truth. Commits sometimes mis-describe their scope; the diff is ground truth.
  2. Sanity-check the state. Stop and tell the user (don't draft) when any of these hold:
    • git log main..HEAD is empty — no commits to describe.
    • Head branch is main.
    • The branch contains merge commits from main that muddy the diff. Offer: "Want me to describe only commits authored on this branch (git log main..HEAD --no-merges), or include the merges?"
  3. Decide whether to ask for framing. Ask the user before drafting only when:

    • The diff spans clearly unrelated themes and the commit titles don't unify them (e.g. one commit is a dep bump, another is an unrelated feature, no shared narrative).
    • The diff is large (>~30 changed files) and commits are terse / generic.

    Otherwise: draft silently. Most branches in this repo are tightly themed — don't manufacture ambiguity.

  4. Pick the title.
    • One line, ≤70 chars, imperative mood, no trailing period.
    • Prefer the dominant conventional-commit prefix from the branch (feat:, fix:, refactor:, docs:, chore:). Fall back to descriptive prose if commits are mixed types.
    • The title should stand on its own — a reader scanning the PR list should understand what's in this PR without opening it.
  5. Write the body. Exactly three H2 sections, in this order:

    ## Summary
    
    1–2 sentences. The "why," not the "what." Name specs implemented,
    issues closed, or design docs referenced — but only if they're
    actually present in the diff or commit messages. Never invent links
    or issue numbers.
    
    ## Changes
    
    Grouped bullets by area. Group labels are derived from the diff;
    typical groups in this repo:
    
    - **Code** — anything under `src/cvclaw/`.
    - **Skills** — `skills/cv-claw/` and `.claude/skills/`.
    - **Docs** — README.md, CLAUDE.md, `.claude/specifications/`.
    - **Templates** — `src/cvclaw/templates/` (the bundled root).
    - **Build/CI** — pyproject.toml, Makefile, .github/.
    
    Skip groups with no changes. Each bullet ≤1 line; reference files
    or subsystems (`src/cvclaw/cli.py`, "ingest.md") rather than commit
    hashes. Bold the group label.
    
    ## Test plan
    
    Markdown checklist. Use only steps the repo actually supports —
    read `Makefile` and `pyproject.toml` to ground each step. For this
    repo that's typically:
    
    - [ ] `make lint` is clean.
    - [ ] `uv run cv-claw render resumes/example.json` succeeds.
    - [ ] Any spec-specific manual smoke tests called out in the
          relevant `.claude/specifications/SPEC-*.md`.
    
    Do not invent CI jobs, test suites, or pytest invocations that
    don't exist in this repo.
  6. Output. Reply with:
    • A single preamble line: PR message for <head>→<base>, drafted from N commit(s) across M changed file(s).
    • A single fenced code block (markdown … ) containing the title on the first line, a blank line, then the body. This makes the whole thing one copy-paste.

Output template

<title>

## Summary

<1–2 sentences>

## Changes

- **<Group>** — <bullet>
- **<Group>** — <bullet>

## Test plan

- [ ] <step>
- [ ] <step>

Conventions (must follow)

  • No emojis anywhere in the title or body.
  • No "🤖 Generated with Claude Code" trailer. That's for gh pr create invocations; this skill produces hand-drafted Markdown the user pastes manually.
  • No Co-Authored-By trailers. Those go on commits, not PR bodies.
  • Three sections only. No Notes / Open questions / Followups section. Caveats fold into Summary or as inline bullets in Changes.
  • Don't fabricate test steps. If a verification step isn't real (no test suite exists, no CI workflow exists), don't list it.
  • Don't reference specs or issues that aren't in the diff or commits. If .claude/specifications/SPEC-foo.md is touched in this PR, mention it; if it isn't, don't.
  • Don't open or edit a PR. This skill writes text. If the user wants the PR opened, they will say so separately and the global gh pr create flow handles it.

Out of scope

  • Running gh pr create / gh pr edit / gh pr view.
  • Choosing reviewers, labels, assignees, milestones, or draft state.
  • Cross-repo PRs or stacked PR chains.
  • Updating an existing PR body in place.

Edge cases

  • Branch is up-to-date with main (no commits ahead). Don't draft; tell the user there's nothing to merge.
  • Branch is behind main. Draft normally, but note in the preamble that the branch is behind and may need a rebase before opening the PR.
  • User asks for a PR message targeting a base other than main (e.g. "PR message into release/0.2"). Honor the requested base; use <base>...HEAD for the diff range.
  • User asks while on main. Stop; ask which branch they meant.
  • Detached HEAD. Stop; ask the user to check out a branch first.

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.