create-branch

por sentry

Crear una rama de git siguiendo las convenciones de nomenclatura de Sentry. Usar cuando se solicite "crear una rama", "nueva rama", "iniciar una rama", "hacer una rama", "cambiar a una nueva…

npx skills add https://github.com/getsentry/skills --skill create-branch

Create Branch

Create a git branch following Sentry naming conventions. Keep this workflow non-interactive unless the user explicitly asks to choose the name manually.

Workflow

  1. Resolve the work description:

    • If $ARGUMENTS is present, use it
    • Otherwise inspect:
      git diff
      git diff --cached
      git status --short
      
    • If there are local changes, derive a short description from the diff
    • If there are no local changes, use a generic description like repo-maintenance, tooling-update, or work-in-progress
  2. Classify the branch type:

TypeUse when
featNew functionality
fixBroken behavior now works
refBehavior stays the same, structure changes
choreMaintenance of existing tooling/config
perfSame behavior, faster
styleVisual or formatting only
docsDocumentation only
testTests only
ciCI/CD config
buildBuild system
metaRepo metadata
licenseLicense changes

When unsure: use feat for new things, ref for restructuring, chore for maintenance.

  1. Generate <type>/<short-description>. Keep <short-description> kebab-case, ASCII-only, and ideally 3 to 6 words.

  2. Choose the base without prompting:

    git branch --show-current
    git remote | grep -qx origin && echo origin || git remote | head -1
    git symbolic-ref refs/remotes/<remote>/HEAD 2>/dev/null | sed 's|refs/remotes/<remote>/||' | tr -d '[:space:]'
    
    • If default branch detection fails, fall back to main, then master, then the current branch
    • If on a detached HEAD, branch from the current commit
    • If already on a non-default branch, branch from the current branch
    • Only switch to the default branch when the user explicitly asks
  3. Avoid collisions by appending -2, -3, and so on until the name is unused locally and remotely.

  4. Create the branch:

    git checkout -b <branch-name>
    

    Report the final branch name, but do not stop for confirmation.

References

Más skills de sentry

architecture-review
sentry
Revisión de salud del código a nivel de equipo. Encuentra módulos monolíticos, fallos silenciosos, brechas de seguridad de tipos, vacíos en la cobertura de pruebas y problemas de compatibilidad con LLM.
pi-agent-integration
sentry
Integrate `@mariozechner/pi-agent-core` as the agent abstraction inside another library or runtime. Use when implementing or refactoring Pi Agent wrappers,…
sentry-debug-issue
sentry
Depurar y corregir un problema de Sentry: localizarlo (por enlace, ID o búsqueda), extraer el contexto completo (stack trace, breadcrumbs, trace, logs) y, opcionalmente, ejecutar el análisis de causa raíz de Seer /…
sentry-svelte-sdk
sentry
Configuración completa del SDK de Sentry para Svelte y SvelteKit. Úsalo cuando te pidan "añadir Sentry a Svelte", "añadir Sentry a SvelteKit", "instalar @sentry/sveltekit" o configurar…
sentry-svelte-sdk
sentry
Configuración completa del SDK de Sentry para Svelte y SvelteKit. Úsalo cuando te pidan "añadir Sentry a Svelte", "añadir Sentry a SvelteKit", "instalar @sentry/sveltekit" o configurar…
skill-scanner
sentry
Escanea habilidades de agente en busca de problemas de seguridad. Úsalo cuando te pidan "escanear una habilidad",
prompt-optimizer
sentry
Crea, optimiza y refina iterativamente prompts de agentes, prompts de sistema, prompts de desarrollador y plantillas de prompts reutilizables. Úsalo cuando se te pida mejorar un…
commit
sentry
commit — una habilidad instalable para agentes de IA, publicada por getsentry/sentry-docs.