alexwickstrom/pm-skills

Two skills that tell you what to do next — across your PRs, and across your board.

Install

What you need

pr-digest degrades gracefully without a tracker — it falls back to matching branches and changed paths, and says so in the report. scrum-master needs the board.

pr-digest

You have six open PRs. Two are red, one has a reviewer waiting on a decision, three are fine. Asking an agent “how are my PRs doing” normally gets you six paragraphs and a check tally.

The rules that get you there:

1. Discover the repo, ticket prefixes, and CI job names at run time — nothing is hardcoded.
2. Order the PRs by real dependency: stacked branches first, then shared files.
3. Surface a review comment only if it’s unresolved, still true, and worth a commit.
4. Collapse CI to one glyph per PR. Never print check tallies.
5. Flag a stale description only when it’s actually wrong — never confirm a non-problem.
6. Sort closest-to-merge first, so the eye lands on today’s wins.
7. Read-only. It never pushes, comments, approves, or merges.

Full text in pr-digest/SKILL.md.

scrum-master

Audits one project board the way a scrum master would: which statuses are lying, which active work has no owner, and where two people are about to build the same thing.

1. Pulls the board and counts it — by status, by assignee, unassigned.
2. Flags the smells: In Progress with no owner, stale In Progress, assigned-but-in-Triage, high priority with no owner, due-date risk, milestones with no staffed critical path.
3. Flags overlap between owners — the highest-value finding, because it names the interface two people need to agree on.
4. Proposes owners by matching unowned work to the lane each person already occupies, and puts anything contested in a needs a joint decision bucket.
5. Has a second agent jq-verify every staleness claim and count before you ever see the report.
6. Changes nothing until you pick action items.

A big unassigned backlog is not a finding. Unowned active, high-priority, or dated work is.

Full text in scrum-master/SKILL.md.

Configure

Both skills take the project name as an argument:

/pm:pr-digest Checkout Revamp
/pm:scrum-master Checkout Revamp between me and Dana

To skip typing it, drop a .claude/pr-digest.json in the repo you use it on. Every key is optional:

{
  "project": "Checkout Revamp",
  "paths": ["services/checkout/", "packages/pricing/"],
  "requiredChecks": ["unit-tests", "lint", "coverage"]
}

• project — the default when you invoke with no argument.
• paths — matches a PR to the project when the PR carries no ticket id.
• requiredChecks — which checks must be green. Without it, the skill trusts whatever GitHub marks required.

Tune it

Fork, edit the SKILL.md, then swap your copy in:

claude plugin uninstall pm@pm-skills         # drop the upstream copy first:
claude plugin marketplace remove pm-skills   # fork and upstream share both names
claude plugin marketplace add /pm-skills
claude plugin install pm@pm-skills

Prefer a bare /pr-digest with no plugin prefix? Use the copy-into-~/.claude/skills/ install above instead of the plugin. You trade the pm: prefix for losing automatic updates.

The output format is the part worth editing. Both skills are opinionated about brevity on purpose — if your team wants the full comment census, loosen Step 4 of pr-digest.

License

MIT.