Generate Conventional Commits messages for staged code and documentation changes.
npx skills add https://github.com/Cogni-DAO/node-template --skill commit-cogni-dao
Please help me install this Agent Skill. Skill: commit Source: https://github.com/Cogni-DAO/node-template/tree/main/.openclaw/skills/commit Command: npx skills add https://github.com/Cogni-DAO/node-template --skill commit-cogni-dao
This Skill automates the creation of well-formatted commit messages, ensuring consistency and adherence to the Conventional Commits specification, which improves project maintainability and automated changelog generation.
type(scope): description format.feat(auth): implement two-factor authentication followed by fix(ui): correct button alignment on login page.Use the commit skill to create a conventional commit message for the staged changes.
High-intent search queries and answers about installing and using this skill.
To generate conventional commit messages for staged git changes, use this Skill to analyze your staged code and documentation updates, automatically creating factual messages formatted as type(scope): description with optional breaking change footers and references.
The conventional commits specification standardizes commit messages into a type(scope): description format, which improves project maintainability by making history readable and enabling automated changelog generation from structured commit metadata.
Yes, you can include breaking change footers and references in automated commit messages. The Skill enforces adherence to the conventional commits specification, supporting optional scopes, factual descriptions, and structured footers for breaking changes.
To write an imperative subject for a conventional commit, the Skill analyzes your staged changes and enforces the specification's requirement for imperative mood, generating factual descriptions like feat(auth): implement two-factor authentication instead of past tense summaries.
Yes, this commit message generator works with both code and documentation changes. It performs objective analysis on all staged modifications to create factual, specification-compliant conventional commit messages regardless of the file type.
Automating conventional commit message generation relies entirely on objective analysis of staged changes, meaning it creates factual descriptions based on code diffs but requires you to stage relevant files first and manually verify the generated type and optional scope accuracy.
mgoodman60Generate descriptive Git commit messages from repository changes with conventional formatting.
ccfGenerate CHANGELOG.md from commits, PRs, and releases using Keep a Changelog.
AnveioAutomate GitHub pull request creation, reviews, feedback, and merges via gh CLI.
rlesniakGenerate conventional commit messages using structured XML templates.