Loading...
Loading...
Found 25 Skills
Generates semantic commit messages following the Conventional Commits specification with proper types, scopes, breaking changes, and footers. Use when users request "write commit message", "conventional commit", "semantic commit", or "format commit".
Generate professional git commit messages following cbea.ms guidelines. Outputs plain copy-pasteable commit message text by default.
A skill for writing Git commit messages. It follows rules combining Conventional Commits and Gitmoji to maintain a consistent commit history.
Create semantic git commits following best practices and Conventional Commits specification.
Generate well-formatted git commit messages following conventional commit standards
Guidance for writing git commit messages that follow the Conventional Commits 1.0.0 specification. Use when preparing commit messages, summarizing code changes for a commit, or validating commit text for compliance.
Read this skill before making git commits
Smart git commit workflow using Conventional Commits format with AI-generated commit message suggestions based on staged changes.
Create a git commit with clear, conventional commit messages. You MUST read this when the user wants to commit staged changes, write a commit message, or finalize code changes with proper conventional commit format since it describes how to follow the user's specific requirements.
Git workflow guidance for commits, branches, and pull requests
This skill MUST be loaded on every git commit without exception. It should also be used when the user asks to "write a conventional commit", "format a commit message", "follow conventional commits spec", "create a semantic commit", "make a commit", "commit changes", or "git commit". Every commit message produced in this project MUST conform to this specification.
Use prefered practices when using git. Use when Codex needs to perform actions with git or Github.