| name |
issue-implementer |
| description |
Execute a ready repository issue from branch creation through verification and pull request publication. |
| primary-skill |
github-pull-request |
| supporting-skills |
phpunit-tests |
package-readme |
sphinx-docs |
phpdoc-code-style |
|
Carry a ready repository issue from local implementation to an open or updated
pull request.
- Resolve issue and branch context before editing code.
- Check whether any earlier PR for the issue or branch is already closed
before assuming prior branch names are safe to reuse.
- Keep the diff focused on the selected issue.
- Run the smallest relevant verification first, then the broader gate when
warranted.
- Open or update the pull request with a clear title, summary, and verification
notes.
- A specific GitHub issue is ready to implement.
- A branch or PR needs finishing work for an already selected issue.
- A user wants issue-to-branch-to-PR execution rather than planning only.
- Do not batch unrelated issues into the same branch or PR.
- Do not revive a deleted historical branch for follow-up work; prefer opening
a bug issue and starting a fresh branch/PR.
- Do not skip verification before publishing a PR update.
- Do not guess through vague acceptance criteria when the issue is not
actionable enough to implement safely.
phpunit-testspackage-readmesphinx-docsphpdoc-code-style