Login
spatie/guidelines-skillsMIT2 files

Spatie Version Control

Apply Spatie's version control conventions when creating commits, branches, pull requests, or managing Git repositories; use for naming repos, writing commit messages, choosing branch strategies, and merging code.

Use this skillView repositoryView on skills.sh
Specification
Skill ID
spatie/guidelines-skills/spatie-version-control
Publisher
spatie
Repository
guidelines-skills
Installs
0
Files
2
License
MIT
Synced
Sep 23, 2026
How to use it

Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.

spatie/guidelines-skills/spatie-version-controlInstalls these files
  • SKILL.md
  • references/spatie-version-control-guidelines.md

What this skill tells the agent

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

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

Core Rules (Summary)

  • Name site repositories after their lowercase naked domain and other repositories with kebab-case.
  • Keep main stable and deployable after launch, and remove stale branches.
  • Use develop during initial development; use feature branches once a project is live.
  • Use only lowercase letters and hyphens in branch names.
  • Write descriptive, present-tense, granular commits.
  • Rebase regularly and generally squash feature branches when merging.
  • Treat history-rewriting and destructive Git commands with the cautions in the reference.

References

  • references/spatie-version-control-guidelines.md

More from spatie

spatie/guidelines-skills

Spatie Javascript

Apply Spatie's JavaScript coding standards for any task that creates, edits, reviews, refactors, or formats JavaScript or TypeScript code; use for variable declarations, comparisons, functions, destructuring, and Prettier configuration to align with Spatie's JS conventions.

spatie/guidelines-skills

Spatie Laravel Php

Apply Spatie's Laravel and PHP coding standards for any task that creates, edits, reviews, refactors, or formats Laravel/PHP code or Blade templates; use for controllers, Eloquent models, routes, config, validation, migrations, tests, and related files to align with Laravel conventions and PSR-12.

spatie/guidelines-skills

Spatie Security

Apply Spatie's security guidelines when configuring applications, databases, servers, credentials, or signed Git commits, or when reviewing code for security concerns; use for SSL setup, CSRF protection, password hashing, database permissions, and server hardening.

Use this skill in a project

Open any RiverX project, search the Skills panel for spatie/guidelines-skills/spatie-version-control, and install it in one click.

Use this skill