pwf-commit-changes

Step 5 — Create Structured Commits

Use this command to produce high-quality, ticket-aware commits after review, including multi-repo parallel commit organization when needed.

Each repo gets its own subagent that:

1. Inspects every changed file individually
2. Groups files by which ticket they relate to
3. Makes multiple focused commits — one per ticket group (plus separate commits for unrelated changes)

All repos run in parallel.

Input

<commit_changes_input> #$ARGUMENTS </commit_changes_input>

If empty, ask:

"Paste the issue(s) or list the ticket number(s) (e.g. TICKET-727, TICKET-726), then I'll commit all uncommitted changes with organized, per-ticket commits."

---

Phase 1 — Parse Tickets

Extract every ticket identifier and its short title from the pasted text:

• Look for Identifier: TICKET-XXX lines; the title is the # Heading above it (or after the last ------ separator).
• Build a list: [{ id: "TICKET-727", title: "Move the BACK TO TABLE button to the right side" }, ...]
• If no ticket is found, subagents will still commit with descriptive subjects but no [TICKET-XXX] prefix.

---

Phase 2 — Discover Repos With Changes

For each workspace path (all paths from context — backend, frontend, *-lambda, etc.):

1. Run: git -C <path> status --short
2. Skip if not a git repo (exit code ≠ 0) or output is empty.
3. Record the repo path and name for repos that have uncommitted changes.

Note: Do NOT collect diffs here. Each subagent will fetch its own per-file diffs in Step 2 of its workflow, allowing precise file-level ticket classification.

Build a list: [{ path, name }] of repos with uncommitted changes.

---

Phase 3 — Spawn One Subagent Per Repo (All in Parallel)

Skill reference: Read skills/commit-changes-repo-worker/SKILL.md once before spawning subagents to understand the multi-commit worker contract.

For each repo with uncommitted changes, invoke one generalPurpose subagent (model: fast) using the Task tool. All invocations run simultaneously.