cocogitto-git-commitlisted

# Cocogitto Git Commit Automation ## Overview This skill ensures that all commits made in this environment strictly adhere to the **Conventional Commits** specification as validated by the `cocogitto` (`cog`) tool. Clean commit histories enable automated versioning, release note generation, and automated changelogs. ## Commit Message Format Each commit message must follow this structure: ```text <type>(<scope>): <description> [optional body] [optional footer(s)] ``` ### Types Allowed - `feat`: A new user-facing feature. - `fix`: A bug fix. - `docs`: Documentation changes only. - `style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.). - `refactor`: A code change that neither fixes a bug nor adds a feature. - `perf`: A code change that improves performance. - `test`: Adding missing tests or correcting existing tests. - `build`: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm). - `ci`: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs). - `chore`: Other changes that don't modify src or test files. - `revert`: Reverts a previous commit. ## Code Example / Command Usage When making a commit, prefer using `cog commit` direct commands over standard `git commit` to ensure validation happens immediately: ```bash # General commit format using cog cog commit <type> "<description>" # Example of a feature commit c