Enforce conventional commit formatting and branch hygiene across repositories.
npx skills add https://github.com/cbown75/ai --skill git-conventions-cbown75
Please help me install this Agent Skill. Skill: git-conventions Source: https://github.com/cbown75/ai/tree/main/.claude/skills/git-conventions Command: npx skills add https://github.com/cbown75/ai --skill git-conventions-cbown75
Git conventions using conventional commits for all repositories. Enforces commit format, branch hygiene, stale branch detection, attribution rules, and PR workflow. Use for all git formatting - ticket-prefix overrides are handled by the dev-workflow skill.
Configure your repository to enforce conventional commits, branch hygiene, and PR workflows as described.
High-intent search queries and answers about installing and using this skill.
Enforcing conventional commits across multiple repositories is achieved by validating commit types, scopes, and branch state to standardize Git workflow hygiene. This ensures clear commit history and predictable automation compatibility across development teams.
Standardizing Git branch naming and PR workflow involves applying disciplined branch hygiene, stale branch detection, and PR-driven collaboration rules. This prevents mainline contamination and supports safe, structured code reviews across repositories.
Yes, this Git workflow approach includes stale branch detection to prevent abandoned work from slipping into production. It maintains clean PRs by identifying and managing inactive branches within your repositories.
Yes, conventional commit formatting supports CI/CD automation triggers by enforcing predictable commit types and scopes. This standardized structure allows automated systems to parse commit history and trigger appropriate deployment pipelines safely.
Conventional commit enforcement focuses strictly on commit formatting, branch hygiene, and PR workflow. It does not handle ticket-prefix overrides, which are managed by separate dev-workflow skills, limiting its scope to repository hygiene and attribution rules.
Attribution rules in a PR-driven Git workflow ensure proper authorship tracking and structured reviews. They standardize how features are developed and merged, maintaining clear accountability across multiple repositories and development teams.
mathiasbourgoinStandardize git commit messages, branch names, and pull request descriptions.
a29paulMerge approved PRs, wait for CI and deployment pipelines, and verify production canary checks.
zeveckCreate and manage Git worktrees with prefix-derived paths and branch overrides.
omarluqEnforce Conventional Commits v1.0.0 standards for branches, worktrees, and commit messages.
