Generate conventional commit messages from the current Git diff.
npx skills add https://github.com/leodiegues/skills --skill commit-msg-leodiegues
Please help me install this Agent Skill. Skill: commit-msg Source: https://github.com/leodiegues/skills/tree/main/skills/commit-msg Command: npx skills add https://github.com/leodiegues/skills --skill commit-msg-leodiegues
It prevents vague or incorrect commit messages by deriving a conventional commit directly from the actual staged diff instead of guessing.
git diff --staged (or git diff) to ground the commit in what actually changed.<scope> from nearest boundary patterns like apps/<name>/, packages/<name>/, services/<name>/, libs/<name>/, modules/<name>/, or src/<module>/, including Nx project naming.feat, fix, refactor, docs, test, chore, ci, perf, build, or style based on behavior and the diff.Use the commit-msg skill to generate a conventional commit message from your current staged changes before you run git commit.
High-intent search queries and answers about installing and using this skill.
You can generate conventional commit messages from a git diff by analyzing staged or unstaged changes to infer the commit type, scope, and a precise subject. This grounds the message in actual file modifications rather than guessing the intent.
Conventional commit scope detection for Nx monorepos works by deriving the scope from nearest boundary patterns like apps, packages, services, or libs directories. It matches these boundaries to Nx project naming configurations for accurate scoping.
Yes, you can use conventional commits for root-level files in a monorepo. The generation process includes sensible handling for root-level files and multi-scope changes, ensuring accurate commit messages even when modifications occur outside standard directory boundaries.
The best way to format conventional commit subjects from staged changes is enforcing subject line constraints such as imperative mood, lowercase, and a maximum of 72 characters. Optional body and footer guidance should follow standard Conventional Commits rules.
Diff analysis chooses between fix, feat, and refactor commit types by evaluating the actual behavior changes and file modifications shown in the diff. It selects the type that accurately matches the development intent behind the staged code alterations.
Conventional commit messages may not match actual code changes if they are written without analyzing the git diff first. Reading the staged diff ensures the commit type, scope, and subject precisely reflect the modified files and behavior.
jeremylongshoreGenerates formatted commit messages from staged changes.
vericontextAutomate VibeFrame version bumps, changelog generation, and commit staging.
mvandermeulenGenerate project changelogs and release notes from Conventional Commits history.
marcioaltoeAnalyze staged and unstaged code changes to generate Conventional Commits messages.