القائمة
Always use this skill for PR creation. Use whenever the user asks to open, create, draft, prepare, or submit a pull request, unless they explicitly ask for raw CLI/API commands instead.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Control Herdr, a terminal multiplexer for coding agents. Use only when the user explicitly mentions Herdr or asks to use Herdr to inspect or control panes, tabs, workspaces, terminals, commands, or communication with another agent. Do not use merely because a task could benefit from a background terminal, delegation, or parallel work. Requires HERDR_ENV=1.
Compact the current conversation into a handoff document for another agent to pick up.
Use when the user says "tuicr review", "/tuicr", "open tuicr", or asks to review local changes in tuicr. Launch tuicr in tmux, then use tuicr's review CLI to read or add comments in TUI review sessions.
Investigate aube package-manager trust, provenance, advisory, or install failures before adding bypasses or package exceptions. Use when `aube install`, `aube add`, `aube audit`, or `mise install` with `npm.package_manager = "aube"` fails on trust policy, provenance, advisories, lifecycle scripts, low downloads, lockfile drift, or another supply-chain gate; also use before adding `trustPolicyExclude`, turning `trustPolicy` off, allowing package builds, or accepting npm packages installed through mise.
Attach an issue or attach a ticket by creating a Platform Linear issue for a PDQ PR or unpushed branch, renaming the branch when needed, updating the PR title, and rerunning the ticketing check.
Verify and pin GitHub Actions versions in workflow files. Use when creating, editing, or reviewing `.github/workflows/*` files, changing `uses:` references, adding external actions, responding to CI/security review feedback about action versions, or checking whether actions are pinned to the latest appropriate version.
| name | open-pr |
| description | Always use this skill for PR creation. Use whenever the user asks to open, create, draft, prepare, or submit a pull request, unless they explicitly ask for raw CLI/API commands instead. |
| disable-model-invocation | true |
gh CLI as the fallback for GitHub operationsgit commands such as status, diff, log, commit, and pushmain or master)git diff <base>...HEADgit log <base>...HEAD --format="%s"git status to check for uncommitted changesFirst, check whether the repository has a PR template. Look in these common locations:
.github/pull_request_template.md.github/PULL_REQUEST_TEMPLATE.md.github/PULL_REQUEST_TEMPLATE/*.mdIf a template exists, use it as the PR body format and fill it in using the conversation context and git context - but keep it concise!
If no template exists, use this fallback template:
# Motivation
[1-2 sentences: what this PR does and why]
# Summary of Changes
- [Key change 1]
- [Key change 2]
- [Key change 3]
# Testing
[How would a human reviewer verify the change from a user perspective when possible - concise bullet point instructions]
# Dependencies/Special Considerations
[only if there are any list them - e.g. other prs that need to be merged, manual
steps that need to be taken - otherwise say "none"]
Guidelines:
Write a short PR title (max 52 characters) - it should always be a in conventional commit style
Ensure the branch is pushed:
git push -u origin HEAD
Create the PR as a draft, preferring GitHub MCP when available and gh CLI otherwise
gh pr create --draft --title "<title>" --body "<body>"
After creating the PR, open it in the browser with open <pr-url>