commit-changes

Automating ticket-based commits across multiple repositories works by grouping modified files by their TICKET-XXX identifiers and creating focused, per-ticket commits in every affected repository using per-repo subagents.

Yes, grouping modified files by ticket number is the core mechanism; the workflow parses pasted issue text containing TICKET-XXX identifiers to ensure files are bundled into the correct focused commits.

The best way to coordinate git commits across multiple workspaces is to spawn per-repo subagents that analyze changes independently and enforce deterministic workflows with strict commit messaging rules defined in rules/commits.mdc.

To create per-repo commits, paste your issue text containing TICKET-XXX identifiers and invoke the commit-changes command; the system will parse the tickets and generate one commit per ticket per repository.

Yes, the workflow enforces strict commit messaging rules for git by following predefined rules in rules/commits.mdc, ensuring every automated commit across the diverse repos maintains a clear and consistent message format.

You should not use automated multirepo commit orchestration when your modified files lack clear TICKET-XXX identifiers, as the workflow depends on parsing those ticket numbers to group files and generate focused commits correctly.