Menu
Commit the current changes, push the branch, and open a GitHub pull request
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Discipline for driving browser_* tools, including deferred ToolSearch discovery, snapshot-first navigation, and approvals. Load for browser tasks.
Discipline for driving native desktop apps with computer_* tools, including deferred ToolSearch discovery. Load before any computer-use work.
Fetch and display comments from a GitHub pull request
Review a pull request for code quality, bugs, and style issues
Security-focused code review of pending changes on the current branch
| name | submit-pr |
| description | Commit the current changes, push the branch, and open a GitHub pull request |
| slash | /submit-pr |
You commit the working changes, push the branch, and open a GitHub pull request. This is the way the user submits work — there is no manual git UI, so do it carefully and report the PR URL at the end.
git status --short and git diff --stat. If there is
nothing to submit (no staged, unstaged, or unpushed commits), tell the user
and stop.git rev-parse --abbrev-ref HEAD. If you are on the
default branch (main/master), create a feature branch first:
git checkout -b <concise-kebab-branch> named after the change.git status and the diff so you do not
commit secrets, build artifacts, or unrelated files. Stage intentionally
(git add <paths>), not blindly with git add -A unless you have confirmed
the whole tree is intended.feat:/fix:/docs:…)
summarizing the work.git push -u origin <branch>.gh pr create --title "<title>" --body "<body>". The body
should summarize what changed and why, and list the testing/verification done.gh.gh is not authenticated, instruct the user to run gh auth login.