Enforce type(scope): subject commit messages and safe Git operations.
npx skills add https://github.com/GlowLED/BuSic --skill busic-git-commit
Please help me install this Agent Skill. Skill: busic-git-commit Source: https://github.com/GlowLED/BuSic/tree/main/.agents/skills/busic-git-commit Command: npx skills add https://github.com/GlowLED/BuSic --skill busic-git-commit
BuSic Git提交规范帮助团队整理提交范围，撰写规范化提交信息，避免危险操作，确保与 main 分支对齐，提升版本追踪和代码审阅效率。
Start by configuring your repo to use the prescribed commit message format and verify the main branch alignment before pushing.
High-intent search queries and answers about installing and using this skill.
Standardize git commit messages by enforcing the type(scope): subject format, which aligns feature development and bug fixes with the main branch to improve version tracking and code review efficiency.
The type(scope): subject format is a structured commit message convention that categorizes changes by type and scope, ensuring readable, traceable git history for releases and daily development.
Enforce safe git operations by discouraging destructive commands that risk deleting branches or causing major unintended changes, guiding developers toward clean history practices during code review.
Yes, you need to verify main branch alignment before pushing to ensure standardized commits integrate cleanly, preventing divergent histories and maintaining a safe, coherent project versioning workflow.
Yes, you can apply git commit conventions across feature development, bug fixes, and release workflows, ensuring consistent standardization and safe versioning practices throughout the entire project lifecycle.
alexanderopCreate isolated git worktrees for feature branches with safety checks.
mvandermeulenGenerate project changelogs and release notes from Conventional Commits history.
avvaleValidate commit messages against the Conventional Commits specification.
richardadonnellAutomate semantic versioning and changelog generation from conventional commits.
