commit

To stage and commit code changes, this skill automatically stages modified tracked files and generates conventional commit messages. It executes preflight checks for linters and formatters, then creates structured commits with type, scope, subject, and body for improved version control.

Conventional commits enforce a structured git commit message format including type, scope, subject, and body. Using this format improves project readability, ensures consistency across version control history, and enables automated changelog generation.

Yes, you can run linters and formatters automatically before a git commit. This skill integrates preflight checks into the staging process, ensuring code quality standards are met before changes are committed to version control.

To stage specific files instead of all modified files, specify the target files when invoking the commit skill. It intelligently handles user-specified file staging while defaulting to staging all tracked changes if no files are explicitly indicated.

The best way to automate git staging and commit message formatting is using a skill that combines automatic staging of modified files with conventional commit enforcement. This triggers preflight code quality checks and generates structured commit messages automatically.

You should not use automated conventional commits when you need manual control over git staging order or custom commit message formatting outside the type, scope, subject, and body structure, as this skill enforces that specific conventional format for all commits.