spatie/guidelines-skills

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.

Ver código fuente

Cómo usar

  1. Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
  2. Consulta las herramientas, credenciales y entornos necesarios en el documento original.
  3. Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/spatie/guidelines-skills --skill spatie-version-control

Antes de empezar

  • La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
  • Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

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

Relacionados por tarea

del mismo repositorio

Más Skills

Todos los Skills