git-commit

To create consistent git commits, this Skill gathers context from your working tree changes and applies repository-specific conventions or conventional commit formatting. It safely stages files and structures the commit subject and body for clear version control tracking.

Conventional commit formatting standardizes commit subjects and bodies using structured prefixes. This Skill applies these conventions automatically from your git diffs when repository-specific rules are absent, ensuring consistent version control history and code quality.

The best way to stage files and create a branch is through structured, safe steps. This Skill handles branch creation and file staging with guardrails around sensitive files, applying conventional commit messages to the resulting changes.

Yes, this git commit workflow respects existing repository conventions when present. It automatically detects repo-specific formatting rules and applies them to your staged changes, falling back to conventional commits only when no custom conventions are found.

Yes, you can use this to handle edge cases when staging sensitive files. The workflow applies safe, structured steps across common edge cases, enforcing guardrails around sensitive files while staging changes and generating commit hashes.

Git commit messages may ignore repository formatting rules if conventions are not automatically detected. This Skill enforces commit subject and body formatting by applying repo-specific conventions when present, or falling back to conventional commits for consistency.