git-commit

To generate conventional commit messages for a monorepo, this skill applies a short conventional commit format with monorepo-specific scope recommendations like web, api, ai, infra, docs, and agent. It splits cross-scope changes into logically grouped multi-commit pipelines, ensuring clear and consistent project history.

Formatting custom commit types like hotfix and design in conventional commits is handled by enforcing the project's specific short format with extended commit types. This ensures every commit message is clear, consistent, and immediately understandable for code review and release note generation.

To plan a multi-commit pipeline for cross-scope changes, the skill generates ordered and logically grouped commits. For example, it separates a bug fix and a documentation update into distinct commits like fix(api) and docs(api), executing them only after explicit user approval.

Yes, preventing accidental modifications to shared git history is achieved through strict safety guardrails. The skill enforces explicit user approval before executing any Git commit operations, ensuring no unintended changes are pushed to the shared project history.

Inconsistent unstructured commit messages hinder code review and debugging by making it difficult to track changes and write release notes. This skill solves the problem by enforcing a standardized conventional commit format for the entire monorepo project.