skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
spatie/guidelines-skills439 installs

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.

How do I install this agent skill?

npx skills add https://github.com/spatie/guidelines-skills --skill spatie-version-control
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill provides version control and Git convention guidelines based on Spatie's public documentation. It contains no malicious patterns, external code dependencies, or execution risks.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerpass

    1/1 file flagged

  • ZeroLeakspass

    Score: 93/100 · 2 sections analyzed

What does this agent skill do?

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

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/spatie/guidelines-skills/spatie-version-control">View spatie-version-control on skillZs</a>