Commit, Push and Open a PR
By cam j · Published · Updated
Stages only the files that belong, writes an accurate commit message, pushes the branch, and opens a pull request with a body reviewers can use.
Prompt template
## Commit, Push and Open a PR Package my current changes into a commit and pull request. - What I changed and why: [textarea: Plain description] - Branch to push: [text: Name or new name] - Base branch: [text: e.g. main] - Commit style: [dropdown: Conventional commits, Plain sentence, Ticket prefix] - Files to leave out: [textarea: Scratch files or unrelated edits] - Open as draft: [toggle: Yes, No] Inspect the working tree first and list changed and untracked files. Stage only files that belong to this change, and flag anything that looks like a secret, a build artifact, or an unrelated edit instead of committing it. Review the staged diff once for leftover debug lines. Write the commit message in the chosen style: a subject under 72 characters in the imperative, then a body that explains why the change was made. If the change has two unrelated parts, make two commits. Push the branch with upstream tracking, never force pushing unless I ask. Open the pull request with a title, a summary, a short list of changes, how it was tested, and any risk. Return the commit hashes and the PR link.