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.
- License 许可
- MIT
- 最近更新
- 2026-07-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- 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.
03 SKILL.md 正文
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.
Repository Naming
Site source code
Use the main domain name in lowercase, without www:
- Good:
spatie.be - Bad:
https://www.spatie.be,www.spatie.be,Spatie.be
Subdomains
Include the subdomain in the repo name:
- Good:
guidelines.spatie.be - Bad:
spatie.be-guidelines
Packages and other projects
Use kebab-case:
- Good:
laravel-backup,spoon - Bad:
LaravelBackup,Spoon
Branches
Initial development
- Maintain
mainanddevelopbranches. - Commit through
develop, not directly tomain. - Feature branches are optional; if used, branch from
develop.
Live projects
- Delete the
developbranch. - All commits to
mainmust come through feature branches. - Prefer squashing commits on merge.
Branch naming
- Use lowercase letters and hyphens only.
- Good:
feature-mailchimp,fix-deliverycosts,updates-june-2016 - Bad:
feature/mailchimp,random-things,develop
Commits
Message format
- Always use present tense.
- Good:
Update deps,Fix vat calculation in delivery costs - Bad:
wip,commit,a lot,solid
Granularity
- Prefer small, focused commits over large ones.
- Use
git add -pfor interactive staging to create granular commits.
Merging
- Rebase regularly to reduce merge conflicts.
- For deploying feature branches: use
git merge <branch> --squash. - If push is denied: use
git rebase(not merge).
Pull Requests
- Optional but useful for peer review, merge validation, and historical reference.
04 同仓库更多 Skills
spatie-security
Apply Spatie's security guidelines when configuring applications, databases, or servers, or when reviewing code for security concerns; use for SSL setup, CSRF protection, password hashing, database permissions, and server hardening.
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-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.
sluggable-development
Use when making a field on an Eloquent model sluggable, generating the migration for a slug column, switching to self-healing URLs, or resolving a model from its slug in a route. Trigger when the request mentions slugs, permalinks, the spatie/laravel-sluggable package, the HasSlug or HasTranslatableSlug trait, the #[Sluggable] attribute, SlugOptions, findBySlug, self-healing URLs, or stale slug redirects in a Laravel project. Covers choosing between the attribute and the trait, generating unique slugs, configuring separator/length/language/scope/uniqueness, preventing slug overwrites, translatable slugs via spatie/laravel-translatable, route model binding through the slug column, self-healing route keys, customizing the 308 redirect through the SelfHealing facade, and overriding the default actions via config/sluggable.php. Do not use for one-off URL-safe strings, signed URLs, or Laravel's built-in Str::slug helper when the result is not stored on a model.
olakunlevpn-filament-skills
Use when writing, reviewing, or refactoring Filament PHP v5 code -- resources, forms, tables, infolists, actions, widgets, panels, relation managers, multi-tenancy, testing, or plugin development. Always apply these standards to all Filament work.
medialibrary-development
Build and work with spatie/laravel-medialibrary features including associating files with Eloquent models, defining media collections and conversions, generating responsive images, and retrieving media URLs and paths.