activitypub-pr-workflow

Name: activitypub-pr-workflow
Availability: InStock
Author: Automattic

Validate ActivityPub PR branch naming, reviewer assignment, and changelog compliance.

576|90|Updated Jul 10, 2018

Search Tags:#git #workflow #changelog #ci/cd #code review #collaboration #pull request #activitypub

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: activitypub-pr-workflow
Source: https://github.com/Automattic/wordpress-activitypub/tree/main/.claude/skills/activitypub-pr-workflow
Command: npx skills add https://github.com/Automattic/wordpress-activitypub --skill activitypub-pr-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Navigating the pull request creation and review process can be daunting, especially with specific project requirements for branch naming, changelogs, and assignments. This Skill simplifies the entire PR workflow, ensuring smooth contributions and faster code integration.

Core Features & Use Cases

Structured PR Creation: Guidelines for branch naming conventions, mandatory assignments, and automated changelog generation, ensuring compliance with project standards.
Development Best Practices: Advice on breaking down features into smaller PRs, performing pre-push checks (linting, testing), and keeping branches updated for a clean history.
Critical Rules: Emphasizes strict requirements regarding AI tool usage and mandatory assignments for every PR, maintaining project integrity and collaboration standards.

Quick Start

Explain the required steps for creating a new feature branch, making changes, and pushing it to the remote repository.

Frequently Asked Questions about activitypub-pr-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I structure pull requests with proper branch naming conventions?▼

Branch naming for ActivityPub PRs must use prefixes add/, update/, fix/, or try/ to categorize the type of change. This naming convention ensures consistent categorization and automated routing of your contributions through the review workflow.

What changelog requirements apply when creating a pull request?▼

Every ActivityPub PR requires either a changelog entry or an explicit Skip Changelog marker. The Skill validates this requirement before PR creation to maintain accurate change documentation and project history.

How do I ensure my PR passes CI and code review checks?▼

Before creating a PR, rebase against trunk, run linting and testing locally, and ensure your changes match .github/PULL_REQUEST_TEMPLATE.md. The Skill validates these technical checks and required CI/lint passes automatically.

What happens with reviewer assignment in the ActivityPub workflow?▼

Reviewer assignment is mandatory for every PR in the ActivityPub repository. The Skill enforces automatic reviewer assignment based on your branch prefix and change type to streamline the code review process.

Can I push directly to the main branch or use any branch naming pattern?▼

No. ActivityPub contributions require specific branch prefixes (add/, update/, fix/, try/) and cannot use arbitrary naming. Direct pushes bypass the workflow validation; use gh pr create to submit changes through the enforced workflow.

What pre-push checks should I perform before submitting a pull request?▼

Run linting and testing locally, verify trunk rebase, and confirm changelog presence or Skip Changelog before pushing. These pre-push checks prevent CI failures and ensure compliance with ActivityPub project standards.