git

Enforce structured commits, branch naming, and submodule handling for Git workflows.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/skaile-ai/ai-assets --skill git-skaile-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/skaile-ai/ai-assets/tree/main/skaile-development/skills/git
Command: npx skills add https://github.com/skaile-ai/ai-assets --skill git-skaile-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Streamlines and enforces robust Git workflows for the skaile-dev monorepo, ensuring consistent commit messages, disciplined branch naming, proper worktree usage, and safe submodule handling across multi-package changes.

Core Features & Use Cases

  • Enforces structured commit messages per the repository's conventions.
  • Manages branch and worktree lifecycles for parallel, isolated work.
  • Supports PR creation, deployment merges, and submodule synchronization.

Quick Start

Describe the change you want to implement and run the git skill to begin a mode (commit, branch, worktree, pr, finish, sync, or deploy).

Frequently Asked Questions about git

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

FAQPage Schema
How do I enforce structured commit messages in a monorepo?

This workflow enforces structured commit messages in a monorepo by validating inputs against a strict commit specification during feature work and deployment merges, emitting a git-state.json file alongside mode execution.

What is the best way to manage Git worktrees for parallel isolated work?

Managing Git worktrees for parallel isolated work is handled by coordinating the full worktree lifecycle, checking for dirty states before operations and ensuring safe submodule synchronization across multi-package changes.

How do I automate branch naming rules for feature development?

Automating branch naming rules for feature development relies on deriving branch names from task descriptions according to predefined naming conventions, ensuring consistent branch lifecycles and safe submodule handling.

Does this Git workflow support submodule synchronization for deploy workflows?

Yes, this Git workflow supports submodule synchronization for deploy workflows by applying mode selection and subagent-dispatch to run tasks, requiring typed confirmation for destructive actions to ensure safe multi-package changes.

What are the limitations of automating destructive Git actions in a monorepo?

When automating destructive Git actions in a monorepo, the workflow checks for dirty worktrees and requires typed confirmation before proceeding, limiting unattended execution to prevent unsafe submodule handling and data loss.