Skip to content

Git-master skill's mandatory commit splitting has no escape hatch #4483

@willmiao

Description

@willmiao

Feature request

The git-master skill enforces a strict commit splitting formula (min_commits = ceil(file_count / 3), different directories must be separate commits, etc.). While atomic commits are a good practice in general, this rule does not account for cases where splitting by directory or file count is counterproductive.

Concrete example

Updating locale/translation files (e.g., messages/en.json, messages/zh.json, messages/ko.json, messages/fr.json). These are identical in nature — the same change applied across languages. The current rules would force splitting them into separate commits ("European languages" / "CJK languages"), which adds no value and clutters the history.

Problem

The splitting behavior is currently not configurable. GitMasterConfigSchema only exposes commit_footer, include_co_authored_by, and git_env_prefix. There is no option to relax or disable the atomic commit enforcement.

Request

Add a configuration option (e.g., enforce_atomic_commits: boolean, default true) to allow users to opt out of the mandatory splitting when it does not fit their workflow.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions