Enforce conventional commit prefixes and AGPL co-author trailers in Git workflows.
npx skills add https://github.com/gunning4it/openorder --skill commit-gunning4it
Please help me install this Agent Skill. Skill: commit Source: https://github.com/gunning4it/openorder/tree/main/.claude/skills/commit Command: npx skills add https://github.com/gunning4it/openorder --skill commit-gunning4it
Conventional commit standards ensure consistent history and accurate attribution, with AGPL co-authorship awareness.
Run the commit helper to generate a compliant conventional commit message following AGPL guidelines.
High-intent search queries and answers about installing and using this skill.
You can enforce conventional commit formats by applying validation rules to prefixes like feat, fix, and docs during pre-commit checks. This ensures consistent Git history and improves changelog generation across feature development and bug fixes.
Adding AGPL co-authorship requires appending specific co-author trailers to your commit messages. This automation guides message construction to ensure correct attribution is applied during staging for compliant commits.
For feature development and bug fixes, you should use prefixes like feat, fix, docs, refactor, test, chore, and perf. Validating these prefixes during pre-commit maintains a clean project history.
Yes, you can validate commit messages in a monorepo by running pre-commit checks. This applies conventional commit standards and AGPL co-authorship rules across all repository changes before they are finalized.
Conventional commit messages fail pre-commit validation when they lack correct prefixes like feat or fix, or miss required AGPL co-author trailers. Applying actionable guidance during message construction resolves these compliance errors.
Room-CStage, format, and push git changes with conventional commits.
plurigridGenerate user-facing changelogs from git commit history.
Kushal9889Sets up Husky git hooks to automate code quality checks and testing before commits.
xloxn69Generate conventional commit messages with type, scope, subject, body, and footer.
