Generate Conventional Commits messages with imperative mood and formatting rules.
npx skills add https://github.com/shirulot/codex-skill --skill caveman-commit-shirulot
Please help me install this Agent Skill. Skill: caveman-commit Source: https://github.com/shirulot/codex-skill/tree/main/caveman-commit Command: npx skills add https://github.com/shirulot/codex-skill --skill caveman-commit-shirulot
This Skill eliminates verbose, noisy, or inconsistent commit messages by enforcing the Conventional Commits standard, ensuring that commit history remains clean and focused on the intent behind changes.
Ask the assistant to generate a commit message for the current changes by typing /caveman-commit.
High-intent search queries and answers about installing and using this skill.
Generate conventional commit messages automatically by applying the Conventional Commits specification to format staged changes into the standard type(scope): description structure. This enforces the specification without manual formatting effort.
The conventional commits format for breaking changes requires specific formatting rules to document the technical reasoning clearly. It applies imperative mood and character limits to ensure version control history remains clean and focused on intent.
Write concise git commit messages for a complex refactor by prioritizing the why over the what. This context-aware summarization highlights technical reasoning and intent without unnecessary fluff, ensuring clear version control history.
Yes, you can use conventional commits for issue tracking in software development. The standard formatting rules support specific syntax for issue tracking, ensuring that commit history remains standardized and clear for version control.
Yes, you need to write commit messages in imperative mood when following the Conventional Commits specification. This requirement ensures that intent-driven version control history remains consistent across the software development workflow.
afterworkGenerate conventional commit messages from staged git changes.
mattg101Stage all changes, commit with a message, and push to a remote Git repository.
damilola-elegbede-orgGenerate conventional commit messages from staged and unstaged Git repository changes.
typemdGather closed issues and commits to draft release notes and create a GitHub draft release.
