conventions-git
/conventions-git
Git and pull-request default conventions — trunk-based branches, conventional commits, atomic commits, history safety, PR size and description. Use when creating branches, writing commit messages, committing, or opening pull requests.
- Author
- bitIO ↗
- Repository
- wheelhouse ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Git and pull-request default conventions — trunk-based branches, conventional commits, atomic commits, history safety, PR size and description. Use when creating branches, writing commit messages, committing, or opening pull requests.
Original author description
Git and pull-request default conventions — trunk-based branches, conventional commits, atomic commits, history safety, PR size and description. Use when creating branches, writing commit messages, committing, or opening pull requests.
How it works
- Branches
- Commits
- History
- Pull requests
SKILL.md preview
--- name: conventions-git description: Git and pull-request default conventions — trunk-based branches, conventional commits, atomic commits, history safety, PR size and description. Use when creating branches, writing commit messages, committing, or opening pull requests. --- The repo's own rules (`AGENTS.md`, commitlint, branch protection, PR template) win over these. Code review itself: `4r-code-review`. ## Branches - **Trunk-based**: short-lived branches off `main`, merged through a PR. - Branch names `<type>/<issue>-<slug>` (e.g. `fix/123-cors-header`) unless the repo defines its own pattern. ## Commits - **Conventional commits**: `type(scope): subject`, with types `feat`, `fix`, `refactor`, `perf`, `test`, `docs`, `build`, `ci`, `chore`, `style`, `revert`. Mark breaking changes with `!` and a `BREAKING CHANGE:` footer. - **Imperative, lowercase subject**, under ~72 characters, no trailing period. The body explains *why*, not *what*. - **One logical change per commit.** Keep refactors and behaviour changes in separate commits. Squash fix-ups before merge. - **Never commit** secrets, `.env` files, dependencies or build output. - **Never bypass hooks** (`--no-verify`) unless the human explicitly agrees. - **As an agent, commit only when the human asked for it** in this session. ## History - Never force-push shared branches. On your own branch, use `--force-with-lease`. - Never rewrite history that others have pulled. ## Pull requests - **Small**: under ~400 changed lines when possible. A bigger PR states why. - **Read your own diff line by line** before asking for review. - **The description says** what changed, why, how to test it and what the risks are, and links the issue (`Closes #123`). - Answer every review comment: accept it, push back with a reason, or open a follow-up.
Versions
The database has no other skills named conventions-git.
Database snapshot: 13.11.2026 · package version 1f477eef2523 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100git-practices
Git conventions for branches, commits, and pull requests. Load this skill whenever creating branches, writing commit messages, or opening PRs. Trigger on any git workflow operation — commits, branches, pull requests, or merge operations. - 96commit
Creates atomic conventional git commits using git-agent. This skill should be used when the user requests "commit", "git commit", "create commit", or wants to commit changes using AI atomic commits. - 91version-control
Expert guidance for Git version control, trunk-based development workflows, and GitHub best practices. Emphasizes Conventional Commits for clean history, short-lived feature branches, frequent integration, and professional collaboration patterns. Use when users need help with… - 96use-git-conventions
Use when repository Git conventions are configured or when branches, commits, pull requests, or issues are created or validated. - 96commit-and-push
Creates atomic conventional git commits using git-agent and pushes changes to the remote repository. Use when the user asks to "commit and push", "commit with git-agent", or wants an atomic AI-generated commit followed by a push. - 100trove-commit
Git commit workflow and message conventions. Use when creating, drafting, or reviewing atomic commits with conventional messages.