Standardize Git commit messages and branch names with Conventional Commits.
npx skills add https://github.com/Wulnut/lark_agent --skill git-commit-wulnut
Please help me install this Agent Skill. Skill: git-commit Source: https://github.com/Wulnut/lark_agent/tree/main/.opencode/skill/git-commit Command: npx skills add https://github.com/Wulnut/lark_agent --skill git-commit-wulnut
Git commit messages and branch naming are often inconsistent, making history hard to read and audits difficult.
Start applying Conventional Commits and the branch naming rules to your repository to maintain a clean history.
High-intent search queries and answers about installing and using this skill.
Standardize Git commit messages by applying Conventional Commits formatting with predefined types like feat, fix, docs, and refactor to keep history readable and audits clear across software development workflows.
Standard branch naming conventions use prefixes like main, develop, feature/*, bugfix/*, release/*, and hotfix/* to keep work organized and maintain a clean traceable history across teams.
Yes, you can apply Conventional Commits to an existing repository by enforcing the format and branch naming rules moving forward to improve future collaboration and traceability without altering past history.
Yes, gentle guardrails prevent automatic commits without prompts, ensure tests pass, keep messages concise, and encourage breaking large changes into small commits to maintain clean branch history.
Feature branches handle new development work while hotfix branches address urgent production issues, both using predefined naming prefixes to keep Git history organized and work traceable across teams.
michaelvolzCreate descriptive git commits from staged and working-tree changes.
FaysilAlshareefGenerate changelogs from git commits using Conventional Commits and Keep a Changelog formats.
GolferGeekRun npm lint, format, test, and build before commits.
eykdCreate git commits following the conventional commit format.
