菜单
Implement a feature or bug fix in Fetch PHP safely and incrementally — locate related code, define expected behavior, change the smallest surface, add PHPUnit tests, update docs, and run the local gates. Use when asked to add functionality, change behavior, or fix a defect in src/Fetch.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Thavarshan/fetch-php --skill fetch-php-implement-change命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Prepare, publish, verify, and recover Fetch PHP releases through Git tags, GitHub Actions, GitHub Releases, and Packagist. Use when asked to make a new release, fix a failed Fetch PHP release, handle Packagist version immutability errors, update release notes, or verify release workflow/tag state for this repository.
Diagnose Fetch PHP GitHub Actions failures — matrix failures across OS (Ubuntu/Windows/macOS) and PHP (8.3/8.4/8.5), prefer-lowest dependency failures, lint/PHPStan, coverage/Codecov, and the docs build. Use when CI is red and you need to find which job failed and why, then reproduce it safely.
Review a Fetch PHP change for correctness, regression risk, public-API/PSR compatibility, static-analysis correctness, test quality, and documentation impact. Use when reviewing a diff, branch, or PR touching src/Fetch, or before opening a PR.
基于 SOC 职业分类
正在显示 SKILL.md
| name | fetch-php-implement-change |
| description | Implement a feature or bug fix in Fetch PHP safely and incrementally — locate related code, define expected behavior, change the smallest surface, add PHPUnit tests, update docs, and run the local gates. Use when asked to add functionality, change behavior, or fix a defect in src/Fetch. |
Follow AGENTS.md for commands, conventions, and boundaries. Use CODE_MAP.md to find the real public surface.
Any code change under src/Fetch/ — new option, new helper, new middleware/event,
bug fix, refactor. For pure test work use fetch-php-test-development; for
diagnosing a failing test/CI use fetch-php-debug-failure.
Locate the seam. Grep CODE_MAP.md and src/Fetch/ for the feature.
Most request behavior flows through ClientHandler + its Concerns/ traits
and Support/RequestOptions / RequestContext. Identify which trait or class
owns the behavior before touching anything.
Define expected behavior in one or two sentences, including error and edge cases (empty/invalid input, async vs sync, streaming, cache/no-cache).
Check public-API impact. If the change touches a public class, interface,
method signature, helper in helpers.php, enum case, exception type, or a
default (retry/timeout/redirect/cache), run fetch-php-public-api-review
first and get maintainer sign-off before a breaking change.
Implement the smallest change that satisfies the behavior. New files get
declare(strict_types=1); and match the surrounding style. Reuse existing
option normalization (RequestOptions) and defaults (Defaults,
RetryDefaults) rather than re-deriving them.
Add/extend tests (fetch-php-test-development): a failing-first test for
bugs, positive + negative paths for features. Keep them offline and
deterministic.
Update docs when behavior or the API changed (fetch-php-documentation-sync)
and add a CHANGELOG.md entry.
Run the gates, narrowest first:
./vendor/bin/phpunit --filter=<yourTest>
composer fix
NO_NETWORK=1 composer check
composer check passes (PHPStan level 6, Duster, full PHPUnit).phpstan.neon ignoreErrors entry to silence a real type problem.sleep(), or wall-clock timing to pass.