dev
Development workflows for WordPress ActivityPub plugin including wp-env setup, testing commands, linting, and build processes. Use when setting up development environment, running tests, checking code quality, building assets, or working with wp-env.
- Installs
- 81
- 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 dev- 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 dev 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 Development Cycle
Quick reference for common development workflows in the WordPress ActivityPub plugin.
Quick Reference
Environment Management
npm run env-start # Start WordPress at http://localhost:8888.
npm run env-stop # Stop WordPress environment.
Testing Commands
npm run env-test # Run all PHP tests.
npm run env-test -- --filter=pattern # Run tests matching pattern.
npm run env-test -- path/to/test.php # Run specific test file.
npm run env-test -- --group=name # Run tests with @group annotation.
npm run test:e2e # Run Playwright E2E tests.
npm run test:e2e:debug # Debug E2E tests.
Code Quality
composer lint # Check PHP coding standards.
composer lint:fix # Auto-fix PHP issues.
npm run lint:js # Check JavaScript.
npm run lint:css # Check CSS styles.
npm run format # Format all code (wp-scripts).
Building Assets
npm run build # Build for production (formatted and minified).
npm run dev # Start development watch mode.
Code Coverage
npm run env-start -- --xdebug=coverage # Start with coverage support.
npm run env-test -- --coverage-text # Generate text coverage report.
npm run env-test -- --coverage-html ./coverage # Generate HTML report.
Comprehensive Documentation
See docs/development-environment.md for detailed setup instructions.
See tests/README.md for comprehensive testing guidance.
See docs/code-linting.md for linting configuration and standards.
Pre-commit Hooks
The repository uses automated pre-commit hooks (.githooks/pre-commit) that run automatically on git commit:
- Sort PHP imports - Automatically organizes use statements.
- Check unused imports - Prevents unused use statements.
- Validate test patterns - Blocks
remove_all_filters('pre_http_request'). - Run PHPCS auto-fix - Applies coding standards automatically.
- Format JavaScript - Runs wp-scripts formatter.
IMPORTANT: Hooks modify staged files automatically. Always review changes before committing. If hooks make changes, you'll need to stage them and commit again.
Setup: Hooks are installed by npm run prepare (runs automatically after npm install).
Common Development Workflows
Initial Setup
git clone git@github.com:Automattic/wordpress-activitypub.git
cd wordpress-activitypub
npm install # Also runs 'npm run prepare' to install hooks.
composer install
npm run env-start # WordPress at http://localhost:8888.
Making Changes Workflow
# 1. Make code changes.
# 2. Run relevant tests.
npm run env-test -- --filter=FeatureName
# 3. Check code quality (optional - pre-commit hook does this).
composer lint
npm run lint:js
# 4. Commit (pre-commit hook runs automatically).
git add .
git commit -m "Description"
# Hook may modify files - review and stage again if needed.
When the admin app imports from a @wordpress/* package that the build externalizes to a wp.* global, check the export against what the plugin's minimum WordPress version ships (wp-includes/js/dist/<package>.js, or typeof wp.<package>.<name> in the browser), not against node_modules. Newer npm versions export names the shipped global does not have.
Before Creating PR
# Run full test suite.
npm run env-test
# Build assets.
npm run build
# Final lint check.
composer lint
npm run lint:js
Debugging Failing Tests
# Run with verbose output.
npm run env-test -- --verbose --filter=test_name
# Run single test file to isolate issue.
npm run env-test -- tests/phpunit/tests/path/to/test.php
# Check test groups.
npm run env-test -- --list-groups
npm run env-test -- --group=specific_group
Fresh Environment
npm run env-stop
npm run env-start
# wp-env automatically sets up WordPress with debug mode and test users.
Key Files
package.json- npm scripts and dependencies.composer.json- PHP dependencies and lint scripts..wp-env.json- wp-env configuration.phpcs.xml- PHP coding standards (custom WordPress rules)..githooks/pre-commit- Pre-commit automation.
FAQ
What does the dev skill do?
Development workflows for WordPress ActivityPub plugin including wp-env setup, testing commands, linting, and build processes. Use when setting up development environment, running tests, checking code quality, building assets, or working with wp-env.
How do I install dev?
Run npx skills add https://github.com/automattic/wordpress-activitypub --skill dev 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/dev/ (personal) or .claude/skills/dev/ (project).
Which AI agents can use dev?
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 dev 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 dev?
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 81 recorded installs.
More from automattic/wordpress-activitypub
code-style
automattic/wordpress-activitypub
Open the skill to read its SKILL.md instructions.
integrations
automattic/wordpress-activitypub
Open the skill to read its SKILL.md instructions.
pr
automattic/wordpress-activitypub
Open the skill to read its SKILL.md instructions.
test
automattic/wordpress-activitypub
Open the skill to read its SKILL.md instructions.
federation
automattic/wordpress-activitypub
Open the skill to read its SKILL.md instructions.
release
automattic/wordpress-activitypub
Open the skill to read its SKILL.md instructions.
Popular testing & qa skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
grilling
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
migrate-to-shoehorn
mattpocock/skills
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
run-train
lllllllama/rigorpilot-skills
Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.
test-driven-development
obra/superpowers
Use when implementing any feature or bugfix, before writing implementation code
finishing-a-development-branch
obra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work