commit-changes-repo-worker

Commit Changes Repo Worker

A focused, self-contained worker that handles one repository end-to-end: inspect files → classify each file by ticket → group → make multiple targeted commits → report.

Spawned as a generalPurpose subagent (model: fast) from the /pwf-commit-changes command. All instances run in parallel (one per repo).

---

Inputs (provided in the parent prompt)

Variable	Description
REPO_PATH	Absolute path to the git repository
REPO_NAME	Short repo name (e.g. frontend, backend)
TICKET_LIST	Newline-separated list of TICKET-XXX: title entries

---

Step 1 — Discover Changed Files

Run:

git -C <REPO_PATH> status --short

Parse the output to get a list of all changed/untracked files (any status: M, A, D, ??, R, etc.).

If the list is empty → skip to Step 5 (nothing_to_commit).

---

Step 2 — Analyze Each File Independently

For every file identified in Step 1, fetch its individual diff:

# For tracked/modified/staged files:
git -C <REPO_PATH> diff HEAD -- "<file>"

# If the above returns nothing (e.g. newly staged or untracked):
git -C <REPO_PATH> diff --cached -- "<file>"

For each file, determine:

• What it does (based on file path + diff content)
• Which ticket from TICKET_LIST it most likely relates to, or NONE

Matching heuristics:

• File name/path aligns with the ticket's feature area (e.g. tasks/ → ticket about tasks)
• Diff content (added/removed lines) matches the ticket description
• If a file clearly belongs to multiple tickets, assign it to the one with the highest coverage
• Config, tooling, migration, and infra files with no clear ticket → assign NONE

Build a map: file → TICKET-XXX (or NONE)

---

Step 3 — Group Files by Ticket

Group all files by their assigned ticket:

Group 1: TICKET-727 → [src/app/features/tasks/components/task-detail/task-detail.component.html]
Group 2: TICKET-726 → [src/app/shared/components/text-input/text-input.component.scss, ...]
Group 3: NONE    → [src/database/migrations/1234567-SomeMigration.ts]