Inventory, classify, and commit related worktree changes with dependency tracing.
npx skills add https://github.com/zeveck/zskills --skill commit-zeveck
Please help me install this Agent Skill. Skill: commit Source: https://github.com/zeveck/zskills/tree/main/skills/commit Command: npx skills add https://github.com/zeveck/zskills --skill commit-zeveck
Safe commit workflows often become error-prone when multiple agents make changes without coordination. This Skill inventories all changes, classifies related vs. unrelated files, traces dependencies, protects other agents' work, and optionally pushes or lands worktree commits.
Describe the current changes to Claude and let it guide a safe, scope-guided commit following the multi-phase workflow.
High-intent search queries and answers about installing and using this skill.
Safe git commits in a multi-agent worktree require inventorying all changes, classifying related files, and tracing dependencies to isolate your work. This prevents accidentally staging or committing unrelated changes from other agents operating in the same workspace.
Isolating staged changes when multiple agents modify a repository involves scope-guided classification of modified files. By inventorying changes and tracing dependencies, you can stage only relevant files and apply safeguards to avoid touching unrelated work.
Dependency tracing for version control commits identifies interconnected files across your workspace to prevent broken builds. It maps related changes so you can stage complete logical units without missing files or accidentally including unrelated modifications.
Yes, you can automate push and land operations for worktree commits in distributed workflows. After safely staging and reviewing scope-guided changes, the workflow can optionally handle push and land operations to integrate your isolated worktree commits.
Git commits include unrelated changes when multi-agent workspaces lack change coordination and scope classification. To fix this, inventory all workspace modifications, classify related versus unrelated files, and apply safeguards to protect other agents' work before staging.
notwillkAggregate git commits, uncommitted changes, and agent knowledge to list changed files.
bdsqqqStage modified files, commit with conventional commits, and push to the remote repository.
patrickhaahrCreate atomic commits from staged git changes with logical grouping.
epologeeGroup git working tree changes into logical commits without pushing.
