skills.rest
J-Pster
J-PsterCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit-changes-repo-worker

Groups changed files by ticket and commits each group separately using git.

291|38|Updated Mar 16, 2026
Search Tags:#automation#git#workflow#commit#repository#ticket#grouping
One-click install
npx skills add https://github.com/J-Pster/Psters_AI_Workflow --skill commit-changes-repo-worker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-changes-repo-worker
Source: https://github.com/J-Pster/Psters_AI_Workflow/tree/main/plugins/psters-ai-workflow/skills/commit-changes-repo-worker
Command: npx skills add https://github.com/J-Pster/Psters_AI_Workflow --skill commit-changes-repo-worker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating per-repo changes across multiple files can become noisy and error-prone. This Skill automatically groups changed files by their related ticket and creates targeted commits for each group, improving traceability and review efficiency.

Core Features & Use Cases

  • Group by ticket: each group becomes a separate commit.
  • Parallelizable: supports running workers per repository to scale across multiple repos.
  • Audit and reporting: provides a clear map of files per commit and a summary of changes.

Quick Start

Run the commit-changes-repo-worker to process a repository's changed files and generate focused commits grouped by ticket.

Frequently Asked Questions about commit-changes-repo-worker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I group changed files by ticket to create separate commits in a git repository?▼

To group changed files by ticket for separate commits, this Skill analyzes file diffs and maps each to a ticket using feature-area heuristics, outputting a structured plan that creates one targeted commit per ticket group.

What is the best way to automate multiple focused commits when working across changed files?▼

Automating focused commits across changed files is done by reading a provided ticket list, mapping the diffs to tickets, and generating multiple targeted commits within the local repository to improve traceability and review efficiency.

Can I run a commit grouping worker per repository to scale across multiple repos?▼

Yes, you can run a commit grouping worker per repository. The workflow is parallelizable, supporting multiple workers to scale the ticket-based commit grouping process across multiple local repositories.

Does this commit grouping workflow require a ticket list to operate?▼

Yes, this commit grouping workflow requires a ticket list. It reads the TICKET_LIST directly from the parent prompt to map diffs and group changed files into focused per-repo commits.

How are changed files mapped to specific tickets when grouping commits?▼

Changed files are mapped to specific tickets by analyzing the diff per file and applying feature-area heuristics to determine the correct ticket association, resulting in a structured commit plan.

What summary or audit output is generated when grouping commits by ticket?▼

When grouping commits by ticket, the workflow generates an audit and reporting output that provides a clear map of files per commit and a summary of all changes made within the repository.

Related Skills

Explore More Software Engineering Skills→
agentclashagentclash
25

git-rules

Validate git commit hygiene and working tree status post-commit.

Official
Basic
vankichivankichi

commit-push-branch

Create branches, commit changes, and push to a Git remote repository.

Community
Intermediate
SennTseSennTse

work-report

Generate daily or weekly work reports from git commits across repositories.

Community
Advanced
ricky-yoshricky-yosh

gf-create-git-commits

Analyze code changes and create atomic git commits organized by intent.

Community
Intermediate