Enforce conventional commit messages and PR title checks.
npx skills add https://github.com/crozzbite/DnDApp --skill github-pr-crozzbite
Please help me install this Agent Skill. Skill: github-pr Source: https://github.com/crozzbite/DnDApp/tree/main/.agent/skills/github-pr Command: npx skills add https://github.com/crozzbite/DnDApp --skill github-pr-crozzbite
Rules for Git, Pull Requests, and Conventional Commits help teams maintain a clean, readable history and enforce consistent practices across repositories. This skill defines the guidelines for commit messages and PRs, making it easier to review changes and automate governance.
Configure your repository to enforce conventional commits and atomic PRs for every change.
High-intent search queries and answers about installing and using this skill.
To enforce conventional commit messages in a git repository, you apply validation rules to commit messages and pull requests, ensuring all entries follow a standard format for reliable changelog generation and history navigation.
Guidelines for maintaining atomic pull requests require clear PR titles, descriptive content, and isolated changes. This ensures effective code reviews and consistent history across repositories without mixing unrelated features.
Yes, you can integrate PR title and description checks into a CI/CD pipeline. This automatically validates pull request structure and conventional commit formats before a merge occurs, standardizing team practices.
Using conventional commits and rebase practices for code history management keeps the project history navigable and clean. It standardizes commit messages and squash practices to enable reliable automated tooling.
No specific dependencies are required to enforce pull request integrity and conventional commits. The guidelines define validation rules for commit messages and PR structure that standardize git history without external tools.
The best way to standardize git history across multiple teams is enforcing conventional commits and atomic PRs. This applies consistent rules for commit messages, rebase practices, and PR descriptions across all repositories.
leodyversemilla07Enforce conventional commit messages and branch naming conventions in Git workflows.
arbazkhan971Generate structured changelogs and release notes from git commit and PR history.
SebastienDegodezVerify unit tests, static analysis, design rules, and conventional commit format.
compartmentdevAutomates git commits compliant with commitlint type/scope and Husky validation.
