Purpose and inputs
Invocation requests the complete implementation-to-PR path. Read the task or plan, repository instructions, branch state, affected docs, and scripts. Do not broaden the request to merge or deployment.
Steps
- Inspect the working tree and current branch. If a new branch is needed, use the repository naming convention and preserve uncommitted work; do not blindly pull into a dirty checkout.
- Implement and review the requested change in complete slices using build.
- Update affected technical docs and nearest README. Run the repository's full pre-push gate (
pnpm qain Basilic); diagnose failures before publishing. - Commit task-owned changes with git-commit, then push with git-push.
- Create or update the PR with git-create-pr. Use the repository PR template. Preserve a
BREAKING CHANGE:footer in the body when the title uses!(squash usesPR_TITLE+PR_BODY). Never open an empty description.
Verification and handoff
- Requested acceptance criteria and required validation pass.
- Commit and push contain only intended work, with hooks enabled.
- PR targets the correct base and explains the final behavior.
Return the commit, branch, PR link, and checks. If a gate fails, report the blocker and the completed local work; do not present an unpublished change as shipped.