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.
npx skills add https://github.com/spatie/guidelines-skills --skill spatie-version-control