القائمة
Commit, push, and create a draft PR using the pr-description format, with UX flow context when relevant.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Reviews code changes for reuse, composition, codebase consistency, and slop. Use when asked to review PRs/diffs, check code reuse, composition, cleanliness, or whether code fits the codebase.
Kick off follow-up work on an existing PR in a parallel tmux/agent session. Use when the user asks to work on a PR, continue a branch, address PR feedback, or resolve merge conflicts in the background.
Kick off a new feature or fix in a parallel clone with Pi working autonomously. Takes a problem description, generates a concise branch name, runs ga to set up the worktree, and sends a crafted prompt to the new Pi session.
Review or refactor code so the correct behavior is the default path; use when APIs, setters, hooks, helpers, or component props have footguns where a natural call bypasses required semantics.
Analyze the current branch's diff from main and related PR to build context for followup requests. Triggers on "prepare context", "branch context", "catch me up", "what's on this branch".
Create UX-first plans as flow trees, then attach concrete function names, files, and implementation anchors after the high-level flow is clear.
| name | create-draft-pr |
| description | Commit, push, and create a draft PR using the pr-description format, with UX flow context when relevant. |
| user-invocable | true |
Commit all changes, push to remote, and create a draft pull request with a focused generated description.
git status to see changesgit diff to understand what changedgit log to see commit message stylemain, create a new branch in the format <initials>/<feature> or the project's branch naming convention, then switch to it-u flagpr-description skill's description format.ux-flow-plan style.gh pr create --draftmain), switch back to main after the PR is createdUse the pr-description skill's format as the base:
## Summary
<One sentence describing the overall change>
- Additional note if needed
- Another note if needed
## Problem
Describe the issue being addressed. What was broken, missing, or suboptimal? Be specific about the root cause.
## Solution
Explain the approach taken to fix the problem. Include code snippets only when they clarify the core approach.
When relevant, add this section between Problem and Solution:
## UX Flow
```text
Current flow
└─ ...
Desired flow
└─ ...
```
Only include UX Flow when it helps explain the product behavior, user journey, or architecture boundary. Keep it short and use the ux-flow-plan tree style.
pr-description as the source of truth for PR body structure.UX Flow from ux-flow-plan only when relevant; omit it for mechanical, dependency, or tiny internal changes.