skill-pull-request

A Spanish-language workflow for creating pull requests and Git branches. A pull request is a proposed code change for review, and a branch is a separate line of development.

In plain words
What is it for?
Use it to create a task-linked branch, prepare a structured pull request, push changes, and follow the project's stated Git conventions.
Why use it?
It removes guesswork about branch names, task links, and the information a reviewer needs to understand and verify a change.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/facturascripts/fs-claude-plugin/skill-pull-request
Any agent
npx skills add FacturaScripts/fs-claude-plugin --skill skill-pull-request
Clone the repo
git clone --depth 1 https://github.com/FacturaScripts/fs-claude-plugin

Made for: Claude Code, Codex.

Per session 130 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,349 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00130 $0.01349
Opus 5 $0.00065 $0.00674
Sonnet 5 $0.00026 $0.00270
Haiku 4.5 $0.00013 $0.00135

Measured 2d ago against content hash 1b0cf84fe1bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

skill-pull-request scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

fs-dev/skills/skill-pull-request/SKILL.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pull Requests y Ramas — Buenas Prácticas

Un buen pull request cuenta una historia: qué problema resuelve, cómo lo resuelve y cómo se puede verificar. El objetivo es que el revisor entienda el contexto sin tener que adivinar, y que el historial del proyecto quede limpio y rastreable.

Creación de ramas

La convención de nombres de rama ayuda a identificar de un vistazo de qué trata cada rama y a vincularla con su tarea correspondiente.

Convención de nombres

Si el usuario proporciona un número de tarea (por ejemplo, 4544), el nombre de la rama debe comenzar con ese número seguido de una descripción corta en kebab-case:

<número-tarea>-<descripción-corta>

Ejemplos:

  • Tarea 4544 sobre descuentos → 4544-descuento-pronto-pago
  • Tarea 3821 sobre informes → 3821-informe-trimestral-iva
  • Tarea 5102 sobre API → 5102-endpoint-clientes

Si no hay número de tarea, usa solo la descripción descriptiva:

fix-calculo-iva-facturas
feat-exportar-csv-clientes
refactor-modelo-presupuestos

Flujo al crear la rama

  1. Asegúrate de estar en la rama base actualizada (main o master): git checkout main && git pull
  2. Crea la nueva rama: git checkout -b <nombre-rama>
  3. Si el usuario dio un número de tarea, confirma el nombre propuesto antes de crearla

Estructura del Pull Request

Usa gh pr create con esta estructura:

gh pr create --title "<título>" --body "$(cat <<'EOF'
## Descripción
<Explicación clara de qué hace esta PR y por qué>

## Tarea relacionada
<Enlace a la tarea si hay número>

## Cambios realizados
<Lista breve de los cambios principales>

## Cómo probar
<Pasos para verificar que funciona correctamente>

🤖 Generado con [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.6 <[email protected]>
EOF
)"

Título de la PR

El título debe ser conciso (menos de 70 caracteres) y describir el cambio principal. Escríbelo en español y en imperativo, igual que los commits:

Ejemplos:

  • "Añadir descuento por pronto pago en facturas"
  • "Corregir cálculo de IVA en informe trimestral"
  • "Refactorizar modelo de presupuestos"

Read the full file on GitHub · 125 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 125 lines · 130 tokens per session scan A 1b0cf84fe1bc

Subscribe to this mod's changes

skill-pull-request is a skill published in the GitHub repository FacturaScripts/fs-claude-plugin (8 stars, last pushed 2mo ago), licensed MIT. It adds 130 tokens to every session and 1,349 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens