Spatie Version Control

This applies Spatie's internal Git conventions to your workflow. It handles repository naming (lowercase domains, kebab-case for packages), branch strategies (main plus develop for new projects, feature branches only for live ones), commit message style (present tense, granular), and merge practices (squash on deploy, rebase to avoid conflicts). It's opinionated the way a mature agency's guidelines are: they've shipped enough client work to know what prevents mess six months later. If you're working on Spatie projects or just want battle-tested conventions instead of arguing about whether to use "fix" or "fixed" in commits, this gives you their playbook.

skills.sh installs: 510
GitHub stars: 98
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add spatie/guidelines-skills --skill spatie-version-control --agent claude-code

Installs into .claude/skills of the current project.

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.

Workflow

Identify the Git operation or repository convention involved.
Read references/spatie-version-control-guidelines.md and focus on the relevant sections.
Apply the project-stage rules before branch, commit, merge, or cleanup guidance.

SKILL.md on GitHub