원클릭으로
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.
// 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.
PHP coding standards and WordPress patterns for ATmosphere plugin. Use when writing PHP code, creating classes, implementing WordPress hooks, or structuring plugin files.
INVOKE THIS SKILL before creating any PR to ensure compliance with branch naming, changelog requirements, and reviewer assignment.
Version management and release processes using Jetpack Changelogger. Use when creating releases, managing changelogs, bumping versions, or preparing releases.
Testing patterns for PHPUnit tests. Use when writing tests, debugging test failures, setting up test coverage, or implementing test patterns for ATmosphere features.
MUST be invoked before creating any PR, pushing a branch for review, or running `gh pr create`. Covers changelog entries, branch naming, PHPCS/PHPUnit checks, and reviewer assignment.
| name | dev |
| description | 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. |
Quick reference for everyday workflows. Full reference: docs/development-environment.md.
# 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.
composer dump-autoload # Regenerate classmap after adding/renaming classes.
# Release.
npm run release # Interactive release script. See the release skill.
admin, password password.# 1. Make changes.
# 2. If a class file was added/renamed:
composer dump-autoload
# 3. Run relevant tests + lint.
npm run env-test -- --filter=FeatureName
composer lint
# 4. Commit.
npm run env -- run cli wp plugin list
npm run env -- run cli wp option get atmosphere_settings
npm run env -- run cli wp transient delete --all
npm run env -- run cli wp db cli
Read docs/development-environment.md when you need:
gh CLI).npm run release, patch releases.