pr

Q: How do I install pr?

Run npx skills add https://github.com/automattic/wordpress-activitypub --skill pr in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/pr/ (personal) or .claude/skills/pr/ (project).

by automattic OfficialCode Quality & Workflow

INVOKE THIS SKILL before creating any PR to ensure compliance with branch naming, changelog requirements, and reviewer assignment.

Installs: 82
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/automattic/wordpress-activitypub --skill pr

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads pr automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

ActivityPub PR Workflow

Branch Naming

Prefix	Use
`add/{feature}`	New features
`update/{feature}`	Iterating on existing features
`fix/{bug}`	Bug fixes
`try/{idea}`	Experimental ideas

Reserved: release/{X.Y.Z} (releases only), trunk (main branch).

Pre-PR Review

Scope the review to what changed — don't review every PR:

Skip for docs-only (*.md, docs/, README), tooling/config-only (.claude/, .agents/, workflow files), and trivial edits (typo, comment, whitespace). Push these straight to PR.
Run the code-review agent only when the branch changes plugin code (PHP/JS/CSS logic). Address any critical issues before proceeding.

PR Creation

Every PR must:

Assign @me
Add Automattic/fediverse as reviewer
Include changelog entry OR "Skip Changelog" label
Pass CI checks
Merge cleanly with trunk

# Create PR (includes required assignment/reviewer)
gh pr create --assignee @me --reviewer Automattic/fediverse

Use the exact template from .github/PULL_REQUEST_TEMPLATE.md — do not create custom formatting.

Write backticks bare in PR bodies and comments. A backslash-escaped backtick renders literally on GitHub, and a single-quoted heredoc needs no escaping anyway.

Changelog

Write changelog messages for end users, not developers. Users read these in the WordPress plugin update screen. Avoid internal jargon (OOM, batching, N+1), class names, or method names. Describe what the user experiences or what changed from their perspective.

✅ Fix automatic cleanup of old activities failing silently on sites with many items.
✅ Add a Site Health check that warns when plugins are causing too many federation updates.
❌ Fix collection purge methods to batch deletions and enforce a hard item cap.
❌ Add Site Health test to detect excessive outbox activity rates.

End all changelog messages with punctuation.

Add manually if forgotten:

composer changelog:add
git add . && git commit -m "Add changelog entry" && git push

See release for complete changelog details.

Workflow

Create Branch

git checkout trunk && git pull origin trunk
git checkout -b fix/notification-issue

Pre-Push Checks

composer lint         # PHP standards (composer lint:fix to auto-fix)
npm run lint:js       # If JS changed
npm run lint:css      # If CSS changed
npm run env-test      # Run tests
npm run build         # If assets changed

See AGENTS.md for complete commands.

Keep Branch Updated

git fetch origin
git rebase origin/trunk
# Resolve conflicts if any
git push --force-with-lease

Special Cases

Hotfixes: Branch fix/critical-issue, minimal changes, add a [Pri] High (or [Pri] BLOCKER) label, request expedited review.

Experimental: Use try/ prefix, mark as draft, get early feedback, convert to proper branch type once confirmed.

Multi-PR features: Create tracking issue, link all PRs, use consistent naming (add/feature-part-1, etc.), merge in order.

Labels

Label	Use
`Bug`	Bug fixes
`Enhancement`	New features
`Docs`	Documentation updates
`Code Quality`	Refactoring, cleanup, etc.
`Skip Changelog`	No changelog needed
`[Status] Needs review`	Ready for review
`[Status] In Progress`	Still working
`[Pri] High` / `[Pri] BLOCKER`	Urgent / expedited

Reference

See docs/pull-request.md for complete workflow details.

FAQ

What does the pr skill do?

INVOKE THIS SKILL before creating any PR to ensure compliance with branch naming, changelog requirements, and reviewer assignment.

How do I install pr?

Run npx skills add https://github.com/automattic/wordpress-activitypub --skill pr in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/pr/ (personal) or .claude/skills/pr/ (project).

Which AI agents can use pr?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is pr safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains pr?

It is published by automattic in automattic/wordpress-activitypub, and it is an official skill from the maker of the technology it covers. It has 82 recorded installs.