A workflow for creating pull requests, which are proposed code changes submitted for review before merging.

Use it to check pending changes, prepare a feature or bug-fix branch, write the pull-request title and description, and assign reviewers.

It helps ensure the changes, branch, title, description, labels, and reviewers are ready and clearly explained.

pr-workflow — Skill for Claude Code by 686f6c61/alfred-dev

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.

Any agent

npx skills add 686f6c61/alfred-dev --skill pr-workflow

Clone the repo

git clone --depth 1 https://github.com/686f6c61/alfred-dev

Made for: Claude Code.

Or install alfred-dev, the plugin that ships this one along with the rest of its 11 skills, 22 commands, 10 agents, 5 hooks, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/686f6c61/alfred-dev/pr-workflow/github.svg)](https://agentmods.dev/skills/686f6c61/alfred-dev/pr-workflow)

Your own site

<a href="https://agentmods.dev/skills/686f6c61/alfred-dev/pr-workflow"><img src="https://agentmods.dev/badge/skills/686f6c61/alfred-dev/pr-workflow/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/686f6c61/alfred-dev/pr-workflow"><img src="https://agentmods.dev/badge/skills/686f6c61/alfred-dev/pr-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 772 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00014	$0.00772
Opus 5.5	$0.00006	$0.00309
Sonnet 5.5	$0.00003	$0.00154
Haiku 4.5	$0.00001	$0.00077

Measured 1mo ago against content hash 7fb178599d9b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pr-workflow 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 1mo 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.

skills/pr-workflow/SKILL.md · 60 lines

How it starts

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

Crear pull requests completas

Resumen

Este skill guia el proceso de creacion de una pull request bien documentada, desde la verificacion de cambios hasta la asignacion de reviewers. Una PR no es solo un mecanismo de merge: es una pieza de comunicacion que explica a los revisores que se ha cambiado, por que y como verificarlo.

El objetivo es que cualquier miembro del equipo pueda entender la PR sin necesidad de leer cada linea de codigo antes de abrir el diff.

Proceso

Verificar el estado de los cambios. Ejecutar git diff y git status para confirmar que los cambios pendientes corresponden a lo que se quiere incluir en la PR. Si hay cambios sin commitear, confirmar con el usuario si deben incluirse o quedarse fuera.
Verificar la rama. Asegurarse de que se trabaja en una rama feature o fix, no directamente en main. Si no existe rama, crearla con un nombre descriptivo: feature/nombre-funcionalidad o fix/descripcion-bug.
Redactar el titulo. El titulo debe tener menos de 70 caracteres y describir el cambio de forma clara. Formato recomendado: tipo: descripcion breve. Ejemplos:
- feat: anadir filtro de busqueda por fecha
- fix: corregir calculo de IVA en facturas
- refactor: extraer logica de validacion a modulo propio

Redactar la descripcion. Seguir esta estructura estandarizada:

## Resumen
- [1-3 puntos explicando que cambia y por que]

## Motivacion
[Por que es necesario este cambio. Enlazar al issue si existe.]

## Plan de pruebas
- [ ] [Pasos concretos para verificar que el cambio funciona]
- [ ] [Comprobaciones de regresion]

## Notas para el revisor
[Contexto adicional, decisiones de diseno, areas que necesitan atencion especial]

Asignar labels. Etiquetar la PR segun el tipo de cambio (bug, feature, refactor, docs) y la prioridad si aplica. Usar gh pr edit --add-label para asignarlas.
Enlazar issues. Si la PR resuelve un issue, incluir Closes #XX en la descripcion para que GitHub lo cierre automaticamente al hacer merge.

Read the full file on GitHub · 60 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.

1mo ago First seen · 60 lines · 14 tokens per session scan A 7fb178599d9b

Subscribe to this mod's changes

pr-workflow is a skill published in the GitHub repository 686f6c61/alfred-dev (117 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 772 once invoked, about $0.0001 per session on Opus 5.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-30.

Claude Code Code review Git and workflow ai-agents automation claude-code-plugin sdlc

code-review

A structured way to examine code changes before or during a merge. It checks both the project's coding standards and whether the change matches its requested behavior.

int2t05/engineering-skills · 27 tokens

oss-polish

A workflow for improving an open-source project's GitHub presentation and public story. It covers the README, repository topics and description, commit history, and positioning among similar projects.

int2t05/engineering-skills · 31 tokens

git-workflow

Perform requested Git actions while preserving user work. Triggers on "commit", "提交".

int2t05/engineering-skills · 22 tokens

refactoring

A workflow for changing a codebase’s structure while keeping its behavior the same. It covers moving code, splitting files and changing dependency boundaries.

int2t05/engineering-skills · 25 tokens

release

Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…

hyhmrright/brooks-lint · 135 tokens

pr

Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.

umputun/cc-thingz · 51 tokens