菜单
Write and run PHPUnit tests. Use whenever a new function/class/endpoint is added or changed, to add or update its unit/integration tests, run the suite (or a single test), and keep coverage meaningful. Default to test-alongside-every-change.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Apache2 (httpd) configuration and ops for PHP services — vhosts, MPM tuning, PHP-FPM via mod_proxy_fcgi, mod_rewrite, TLS/HTTP2, compression/caching, hardening, and diagnosing 5xx/perf issues. Use for web-server config, deployment topology, and Apache performance/security.
Test automation strategy and engineering across the pyramid — unit, integration, API/contract, and end-to-end. Use for designing a test strategy, building API/E2E suites, CI test pipelines, fixtures/factories, flake reduction, and coverage of a REST microservice. Complements phpunit-testing for cross-cutting and higher-level testing.
MySQL schema design, indexing, and query tuning. Use when modeling tables, choosing types/keys, writing or optimizing SQL, reading EXPLAIN output, or resolving slow queries, deadlocks, and transaction issues.
Modern PHP 8.4/8.5 authoring and review. Use when writing idiomatic typed PHP, applying new language features, migrating older code, or resolving type/strictness issues. State the minimum PHP version any recent feature requires.
PHP performance — profiling, removing hotspots, cutting latency/memory, OPcache/JIT/preloading, eliminating N+1, efficient structures, generators/streaming, connection reuse, benchmarking. Use when something is slow or memory-heavy, or to validate an optimization. Measure first.
Redis from PHP — caching, sessions, rate limiting, locks, queues/streams, pub/sub, sorted-set patterns, TTL/eviction. Use when adding Redis to a feature, designing key schemes, or fixing cache correctness/stampede issues.
| name | phpunit-testing |
| description | Write and run PHPUnit tests. Use whenever a new function/class/endpoint is added or changed, to add or update its unit/integration tests, run the suite (or a single test), and keep coverage meaningful. Default to test-alongside-every-change. |
Policy: every new or changed function gets a test in the same change. Don't consider a feature done until its tests exist and pass.
tests/, mirroring src/ namespaces (PSR-4 Tests\ autoload in composer.json autoload-dev).phpunit.xml. Use the current PHPUnit major (11/12): attributes (#[Test], #[DataProvider], #[CoversClass]) over the old @ annotations.*Test.php, classes final class XxxTest extends TestCase.composer install
vendor/bin/phpunit # full suite
vendor/bin/phpunit tests/Unit/FooTest.php # one file
vendor/bin/phpunit --filter testCreatesUser # one test by name
vendor/bin/phpunit --coverage-text # coverage (needs Xdebug/PCOV)
If no Composer/PHPUnit setup exists yet, scaffold it: composer require --dev phpunit/phpunit, add a phpunit.xml, wire autoload-dev, and add a composer test script.
testRejectsDuplicateEmail).expectException). Use #[DataProvider] for input matrices.tests/Integration/) with real MySQL/Redis fixtures and transactional rollback.After adding code, add/adjust the test, run the relevant test, and report pass/fail with the actual output. For broad test-strategy or non-PHPUnit automation, use automation-tester-specialist.