القائمة
Decompose the working tree into clean commits and open a PR. Use when the user asks to ship the current change end-to-end.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create a feature branch using this repo's branch-naming conventions.
Creates a new vcs branch. Should rarely be called directly.
Create a commit following this repo's conventions (Conventional Commits). Use when the user asks to commit changes. Optional file list scopes the commit.
Creates a vcs commit. Should rarely be called directly.
Opens a vcs pull request. Should rarely be called directly.
Partition the current working tree into the smallest coherent commit chunks. Use when a diff spans multiple concerns and needs to be split.
| name | commit-and-push |
| description | Decompose the working tree into clean commits and open a PR. Use when the user asks to ship the current change end-to-end. |
End-to-end ship flow: messy working tree → clean commit chunks → pushed branch → open PR.
This skill is pure composition — it only invokes capability-layer skills.
Plan the chunks. Invoke /identify-commits. It reads the working
tree, proposes the smallest coherent commit chunks, and waits for the
user to approve or edit the plan. Capture the approved plan.
(Conditional) Create branch. If you are not on a feature branch,
invoke /branch to create one. The branch name should reflect the
overall intent of the change, not the individual commit chunks.
Commit each chunk. For each chunk in the approved plan, in order:
/commit <chunk.files...>
The capability skill stages the listed files, writes a
Conventional-Commits message, and invokes commit-vcs to create the
commit. Collect the commit hash it reports.
Open the PR. Invoke /pr. It refuses if we're on main, pushes
the branch, renders the PR body from
docs/harness/vcs/pr-template.md, and invokes pr-vcs to open the PR.
Report. Print one line per commit (<hash> <subject>) followed
by the PR URL from /pr.
commit-vcs, pr-vcs) directly. Always goes
through the capability layer./identify-commits' plan, stop. The
orchestration is a coordinator, not a decision-maker.