
Spatie Version Control
- 333 installs
- 88 repo stars
- Updated April 27, 2026
- spatie/guidelines-skills
spatie-version-control is a Git & Pull Requests agent skill that applies Spatie's version control conventions for commits, branches, pull requests, repository naming, and merge strategies in agent-assisted development wo
About
spatie-version-control is an MIT-licensed Spatie guidelines skill that encodes the company's Git and version control conventions for consistent repository management across agent-assisted workflows. It activates when creating commits, branches, or pull requests, naming new repositories, or choosing branching and merging strategies, keeping message format, branch naming, and PR hygiene aligned with Spatie engineering standards. Developers reach for spatie-version-control in Claude Code, Cursor, or Codex sessions where multiple contributors and agents touch the same repo and ad-hoc Git habits would create noisy history or inconsistent review artifacts. The skill scopes strictly to Git operations, repository naming, and merge policy guidance rather than application runtime code, making it a lightweight review companion from spatie/guidelines-skills for teams already following or adopting Spatie open-source practices.
- spatie-version-control
- AI & Agent Building
- AI-coding skill
Spatie Version Control by the numbers
- 333 all-time installs (skills.sh)
- +8 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #2,194 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/spatie/guidelines-skills --skill spatie-version-controlAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 333 |
|---|---|
| repo stars | ★ 88 |
| Last updated | April 27, 2026 |
| Repository | spatie/guidelines-skills ↗ |
How do you follow Spatie Git commit and PR conventions?
Helps with ai & agent building tasks.
Who is it for?
Developers and agents working on Spatie-style PHP or Laravel repositories who want consistent Git history and PR formatting.
Skip if: Repositories following conventional commits only, GitHub Actions CI authoring, or teams that do not want opinionated Spatie naming rules.
When should I use this skill?
A developer creates commits, branches, pull requests, names a new repository, or asks about Spatie branching and merging strategy.
What you get
Spatie-compliant commit messages, branch names, pull request descriptions, and merge strategy choices aligned with repository guidelines.
- Convention-compliant commit messages
- Branch and PR formatting guidance
Files
Spatie Version Control Guidelines
Overview
Apply Spatie's Git and version control conventions for consistent repository management.
When to Activate
- Activate this skill when creating commits, branches, or pull requests.
- Activate this skill when naming new repositories.
- Activate this skill when deciding on branching or merging strategies.
Scope
- In scope: Git operations, repository naming, branch naming, commit messages, merge strategies.
- Out of scope: Code style, deployment pipelines, CI/CD configuration.
Repository Naming
Site source code
Use the main domain name in lowercase, without www:
- Good:
spatie.be - Bad:
https://www.spatie.be,www.spatie.be,Spatie.be
Subdomains
Include the subdomain in the repo name:
- Good:
guidelines.spatie.be - Bad:
spatie.be-guidelines
Packages and other projects
Use kebab-case:
- Good:
laravel-backup,spoon - Bad:
LaravelBackup,Spoon
Branches
Initial development
- Maintain
mainanddevelopbranches. - Commit through
develop, not directly tomain. - Feature branches are optional; if used, branch from
develop.
Live projects
- Delete the
developbranch. - All commits to
mainmust come through feature branches. - Prefer squashing commits on merge.
Branch naming
- Use lowercase letters and hyphens only.
- Good:
feature-mailchimp,fix-deliverycosts,updates-june-2016 - Bad:
feature/mailchimp,random-things,develop
Commits
Message format
- Always use present tense.
- Good:
Update deps,Fix vat calculation in delivery costs - Bad:
wip,commit,a lot,solid
Granularity
- Prefer small, focused commits over large ones.
- Use
git add -pfor interactive staging to create granular commits.
Merging
- Rebase regularly to reduce merge conflicts.
- For deploying feature branches: use
git merge <branch> --squash. - If push is denied: use
git rebase(not merge).
Pull Requests
- Optional but useful for peer review, merge validation, and historical reference.
---
Source: https://spatie.be/guidelines/version-control
Related skills
FAQ
What does spatie-version-control cover?
spatie-version-control covers Git operations, repository naming, commit messages, branch strategies, pull request formatting, and merge policies per Spatie guidelines. It does not handle application runtime code or CI pipeline configuration.
When should agents activate spatie-version-control?
spatie-version-control activates when creating commits, branches, or pull requests, naming repositories, or deciding branching and merging strategies. The skill is MIT-licensed and authored by Spatie in the guidelines-skills repository.