mcpField
S
spatie-version-control

spatie-version-control

github.com/spatieDevelopment97491 installsUpdated 6d ago
Repository

About spatie-version-control

A coding skill that applies Spatie's conventions for Git and repository management. It covers naming, branching, commits, merging, and guidance for handling destructive commands.

Key features

  1. 01Repository and branch naming
  2. 02Project-stage branching guidance
  3. 03Commit message conventions
  4. 04Rebase and merge guidance
  5. 05Cautions for destructive Git commands

Use cases

  1. 01Choosing a repository or branch name
  2. 02Preparing granular commit messages
  3. 03Planning a merge or branch cleanup

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/spatie/guidelines-skills --skill spatie-version-control

After installing, type/spatie-version-controlin Claude Code to confirm it loaded.

Bundled filesreferences/spatie-version-control-guidelines.md

Details

From the project README

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

Comments

Markdown supported