commit-multi-repo

Coordinate multi-repository commits across parent and submodules with staged verification.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/NagasakaH/dev-process --skill commit-multi-repo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-multi-repo
Source: https://github.com/NagasakaH/dev-process/tree/main/.claude/skills/development/commit-multi-repo
Command: npx skills add https://github.com/NagasakaH/dev-process --skill commit-multi-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

サブモジュールを含むリポジトリ群で、複数リポジトリにまたがる変更を整然とコミットするためのマルチリポジトリ対応コミットスキル。親リポジトリとサブモジュール間の参照整合性を保ち、ビルド成果物や一時ファイルの除外を適用し、ステージング確認を経てサブモジュール先行のコミット順序を実現します。

Core Features & Use Cases

  • サブモジュールを含む複数リポジトリの変更を一元管理
  • 不要ファイルの自動除外と変更内容の整合性チェック
  • サブモジュール→本リポジトリの順序でのコミット実行と履歴整合性の維持
  • 日本語コミットメッセージの自動生成規則と MR 提案の自動作成
  • Use Case: サブモジュールの仕様変更を親リポジトリへ安全に適用するワークフロー

Quick Start

Run the multi-repo commit skill to coordinate submodule and parent repository changes, then confirm the staging before committing.

Frequently Asked Questions about commit-multi-repo

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

FAQPage Schema
How do I coordinate multi-repo commits across parent and submodules?

Multi-repo commit coordination is handled by enforcing a submodule-first commit order, verifying staged changes, and excluding build artifacts to maintain cross-repository history consistency.

What is the correct commit order for git submodules and parent repositories?

The correct commit order is submodule-first. This Skill enforces this deterministic sequence to ensure parent repository references remain intact and consistent across repositories.

How do I exclude build artifacts when committing multiple git repositories?

Artifact exclusion is automatically applied during the multi-repo commit process. This Skill filters out build artifacts and temporary files before verifying staged changes and executing commits.

Can I generate Japanese commit messages for multi-repo git workflows?

Japanese commit messages are automatically generated for both submodules and the main repository, ensuring standardized and deterministic historical records across multi-repo git workflows.

What are the limitations of automated multi-repo git commits?

This multi-repo commit Skill applies specifically to repositories with submodules and requires prior staging of changes. It provides staging reports and rollback guidance rather than automatic conflict resolution.