Agent Skills › relaticle/relaticle › spatie-version-control

spatie-version-control

GitHub

应用 Spatie 的 Git 版本控制规范，涵盖仓库命名、分支策略、提交信息及合并流程，确保代码库管理的一致性。

.claude/skills/spatie-version-control/SKILL.md relaticle/relaticle

Trigger Scenarios

创建提交管理分支处理拉取请求仓库命名

Install

npx skills add relaticle/relaticle --skill spatie-version-control -g -y

More Options

Non-standard path

npx skills add https://github.com/relaticle/relaticle/tree/main/.claude/skills/spatie-version-control -g -y

Use without installing

npx skills use relaticle/relaticle@spatie-version-control

指定 Agent (Claude Code)

npx skills add relaticle/relaticle --skill spatie-version-control -a claude-code -g -y

安装 repo 全部 skill

npx skills add relaticle/relaticle --all -g -y

预览 repo 内 skill

npx skills add relaticle/relaticle --list

SKILL.md

Frontmatter

{
    "name": "spatie-version-control",
    "license": "MIT",
    "metadata": {
        "author": "Spatie"
    },
    "description": "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."
}

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.

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.