Detect conventional commit types from git changes and file patterns.
npx skills add https://github.com/fusengine/agents --skill commit-detection
Please help me install this Agent Skill. Skill: commit-detection Source: https://github.com/fusengine/agents/tree/main/plugins/commit-pro/skills/commit-detection Command: npx skills add https://github.com/fusengine/agents --skill commit-detection
This Skill helps developers determine the most appropriate conventional commit type (e.g., feat, fix, chore) based on the nature of their code changes, ensuring consistent and informative commit messages.
fix commit type, potentially with a scope like api if the fix is in the API layer.Use the commit-detection skill to analyze the current staged changes and suggest a commit type.
High-intent search queries and answers about installing and using this skill.
To determine the correct conventional commit type from a git diff, analyze modified files, change statistics, and diff content. Categorize files into types like docs, test, config, and src to apply predefined rules for suggesting commit types such as feat or fix.
Commit scope detection works by identifying the primary directory of changed files in your git repository. It analyzes file paths from your staged changes to determine the relevant scope, ensuring consistent and informative commit messages for specific modules.
Yes, you can automatically suggest a fix commit type by analyzing modified test and src files. The mechanism categorizes modified files by type and applies predefined rules to the diff content, determining whether a fix, feat, or chore type is appropriate.
The best way to categorize git changes for conventional commits is to group modified files into predefined types like docs, test, config, and src. This categorization applies predefined rules to analyze change statistics and suggest the optimal commit type.
Yes, conventional commit detection works without external dependencies. It uses internal references to analyze git changes and file patterns, requiring only your staged git diff to suggest the commit type and scope.
Your commit type suggestion defaults to chore for configuration file changes because the detection mechanism categorizes config files separately from src or docs. It applies predefined rules to these file patterns to ensure the commit type matches the maintenance nature of the changes.
wikimediaFetch a Gerrit change by ID and generate a structured code review.
xztxyGenerate conventional commit messages with type, scope, and description.
avvaleValidate commit messages against the Conventional Commits specification.
angelriera-devAnalyze staged diffs to generate conventional commit messages with safety checks.