Skip to content

Automattic/wordpress-atmosphere / .agents/skills/dev

Development workflows for WordPress ATmosphere plugin including wp-env setup, testing commands, linting, and build processes. Use when setting up development environment, running tests, checking code quality, or working with wp-env.

ATmosphere Development Cycle

Quick reference for everyday workflows. Full reference: docs/development-environment.md.

Core Commands

# Environment.
npm run env-start            # WordPress at http://localhost:8884.
npm run env-stop

# Tests.
npm run env-test                            # All PHP tests.
npm run env-test -- --filter=pattern        # Subset by name.
npm run env-test -- --group=name            # Subset by @group.
composer test                               # Local (needs MySQL).

# Code quality.
composer lint                # PHPCS check.
composer lint:fix            # PHPCS auto-fix.

# Release.
npm run release              # Interactive release script. See the release skill.

Default URLs

Typical Loop

# 1. Make changes.
# 2. Run relevant tests + lint.
npm run env-test -- --filter=FeatureName
composer lint

# 3. Commit.

WP-CLI Inside wp-env

Go through the env npm script, which runs the project's own @wordpress/env. Don't use npx wp-env: wp-env on npm is an unrelated package, and npx downloads and runs it whenever the local binary isn't found.

npm run env -- run cli -- wp plugin list
npm run env -- run cli -- wp option get atmosphere_identity
npm run env -- run cli -- wp post create --post_title='Test' --post_status=publish --porcelain
npm run env -- run cli -- wp transient delete --all
npm run env -- run tests-cli -- wp option list     # Same, against the tests instance (:8885).

When to Read the Full Docs

Read docs/development-environment.md when you need:

  • Prerequisites (Node version, Docker setup, Composer, gh CLI).
  • Troubleshooting (Docker not running, port conflicts, DB connection errors, slow performance on macOS).
  • Code coverage (Xdebug coverage mode, HTML coverage reports).
  • PHPUnit argument reference (every flag we use).
  • wp-env configuration (overriding PHP / WP versions, mounts, custom ports).

Related Skills

  • code-style — PHP conventions, hooks, security, error handling.
  • test — PHPUnit patterns, the Publisher capture fixture, simulating in-flight races.
  • pr — pre-PR checklist, commit format, special situations.
  • release — npm run release, patch releases.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 319kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 319kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 319kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 196kUpdated Claude CodeCodexVerifiedInstall