仓库原始内容
按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
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.mdand 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
mainstable and deployable after launch, and remove stale branches. - Use
developduring 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
