workspace-commit

Coordinate commits and pushes across all git repos in a workspace.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/dlepaux/dotfiles --skill workspace-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workspace-commit
Source: https://github.com/dlepaux/dotfiles/tree/main/.claude/skills/workspace-commit
Command: npx skills add https://github.com/dlepaux/dotfiles --skill workspace-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains consistency across a workspace by coordinating commits and pushes across the root repository and all nested independent repos.

Core Features & Use Cases

  • Discover and enumerate all git repos within a workspace (root and one-level nested repos).
  • Detect dirty repos, warn on merge conflicts or detached HEADs, and provide a summary before pushing.
  • Stage changes, commit with conventional messages, and push to each repo's remote while preserving independent histories.

Quick Start

Commit and push all changes across every git repository in the current workspace.

Frequently Asked Questions about workspace-commit

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

FAQPage Schema
How do I commit and push changes across multiple git repositories in a workspace?

You can coordinate commits and pushes across multiple git repositories by automating the discovery of nested repos, staging changes, applying conventional commit messages, and pushing to each remote while preserving independent histories.

What is the best way to synchronize updates across a root repository and nested subrepos?

Synchronizing updates across a root repository and nested subrepos is done by coordinating commits and pushes across the workspace, ensuring unified history and synchronized updates without relying on submodules.

Can I detect dirty worktrees and merge conflicts before pushing multiple git repos?

Yes, you can detect dirty worktrees and receive warnings on merge conflicts or detached HEADs before pushing, providing a status summary to ensure clean synchronization across the workspace.

Does workspace multi-repo automation work with conventional commit messages and independent histories?

Multi-repo automation works with conventional commit messages by staging changes and committing to each repository while preserving their independent histories during the push to remotes.

What are the limitations of automating multi-repo git workflows in a workspace?

Limitations include avoiding submodules and detached HEADs, as the automation specifically targets workspaces hosting a root repository plus one-level nested independent repos to maintain consistent synchronization.