agentsclimarketplace

Pr description

Skill K95M65/AI_ONBOARD/skills/pr-description

Portable agent workflow framework for Codex, Claude Code, and OpenCode—shared project context, focused skills, independent review, and safe updates.

Install
npx -y skills add K95M65/AI_ONBOARD --skill pr-description

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 21 days oldThe repository was created 21 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Write a clear pull-request description from the branch's commits and diff. Use when opening a PR or when asked to summarize a branch's changes for review.

SKILL.md

1.2 KB, 239 tokens by cl100k_base, as published. Nobody here has run it

PR description

When to use

Opening a PR, or summarizing a branch's changes for reviewers.

Steps

  1. Gather the raw material: bash scripts/collect.sh [base] (base defaults to origin/main, falling back to main). It prints the commit subjects and the changed-file stat for base..HEAD.
  2. Write the description from that material using the template below — explain the why, not just the what; the diff already shows the what.
  3. Keep it honest: call out risk, follow-ups, and anything not covered by tests.

Template

## Summary
<1–3 sentences: what this PR does and why.>

## Changes
- <the notable changes, grouped; not a commit dump>

## Testing
- <what you ran / added, and the result>

## Risk & follow-ups
- <blast radius, migrations, anything deferred>

Notes

  • Lead with the problem being solved, not the implementation.
  • If the branch does several unrelated things, that's a signal to split the PR, not to write a longer summary.

What ships with it: 1 file

899 B alongside SKILL.md, 1 of them executable

scripts/

Gives 0 of the 12 instructions most pr commit review skills give in 239 tokens

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-07

  • Use conventional commits formatin 127 of 888, across 115 files
  • Keep subject line under 72 charactersin 62 of 888, across 48 files
  • Delete branches after mergein 51 of 888, across 38 files
  • Use imperative mood in subject linein 51 of 888, across 42 files
  • Use imperative mood in commit messagesin 44 of 888
  • Verify directory is ignored before creating worktreein 43 of 888, across 12 files
  • Generate a conventional commit messagein 43 of 888
  • Add unignored worktree directories to gitignorein 42 of 888, across 10 files
  • Make atomic commitsin 39 of 888, across 27 files
  • Run tests before committingin 36 of 888, across 25 files
  • Verify clean test baselinein 35 of 888, across 9 files
  • Split unrelated changes into separate commitsin 35 of 888, across 30 files

Said here and by no other author read

  • Gather commits and diff stat from the base branch
  • Write the description from that material
  • Call out risks and uncovered testing
  • Group notable changes in the description
  • Lead with the problem being solved

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 327,132. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.