dyad-pr-push

name	dyad:pr-push
description	Publish local work by committing changes, running checks, pushing the branch, and creating or refreshing a GitHub PR with a reviewer-useful description.

PR Push

Use this skill to publish the current work to GitHub. It must complete autonomously and push by the end unless GitHub auth or permissions block the operation.

Workflow

1. Run /remember-learnings first. This captures session learnings before any push or PR creation, so any resulting AGENTS.md or rules/ changes are included in the same publish flow.

2. Decide whether to run unit tests locally before publishing. For broad or cross-cutting changes, run npm test. For targeted changes, run the narrowest relevant test command, such as npm test -- path/to/file.test.ts. For docs, agent-config, or other low-risk changes, it is acceptable to skip local unit tests because GitHub CI will run the full suite.

3. Review the complete branch diff and commit range against the base branch. Write:

   • A descriptive commit message for newly staged work.
   • A concise PR title describing the user-visible outcome or engineering purpose.
   • A reviewer-useful PR body with a ## Summary section.

   Start the summary with a 1-2 sentence overview of the purpose and outcome, then add bullets for the decisions that deserve reviewer attention. Focus those bullets on subjective choices, trade-offs, assumptions, intentional exclusions, behavior boundaries, and questions a reviewer should verify. Use as many bullets as the change needs; optimize for helping a reviewer decide whether the approach is right, not for terseness or narrating the diff.

   Do not add a routine ## Testing section. Report verification commands and results in the final handoff instead. Stay close to the user's original intent, and do not use changed filenames as a summary, merely restate commit subjects, or rely on an automated reviewer to explain the change later.