Agent skill

PR Workflow

by 686f6c61 in 686f6c61/alfred-dev

Crear pull requests completas con descripcion, labels y reviewers

MITAuto-check passedDevelopment

Install PR Workflow

skills CLI
$ npx skills add 686f6c61/alfred-dev --skill pr-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install 686f6c61/alfred-dev pr-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/686f6c61/alfred-dev.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pr-workflow .claude/skills/pr-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pr-workflow
GitHub stars
117
Token cost
~777 tokens
SKILL.md length
398 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Crear pull requests completas con descripcion, labels y reviewers

  • Works in 9 steps: Verificar el estado de los cambios.… → Verificar la rama. Asegurarse de que se… → Redactar el titulo. El titulo debe tener… → …
  • Tasks that involve Pull requests
  • SKILL.md covers Resumen, Proceso and Que NO hacer
  • Calls gh and git

What it does

PR Workflow is an agent skill from 686f6c61/alfred-dev. Crear pull requests completas con descripcion, labels y reviewers

Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. The repository describes itself as: Tu equipo de desarrolladores en un plugin. 10 agentes, 11 skills planas, 18 comandos /alfred-dev:. Memoria persistente, quality gates con evidencia y MCP local. The licence is MIT.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/pr-workflow”

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Verificar el estado de los cambios. Ejecutar git diff y git status para confirmar que los cambios pendientes corresponden a lo que se…
  2. 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…
  3. Redactar el titulo. El titulo debe tener menos de 70 caracteres y describir el cambio de forma clara. Formato recomendado: tipo…
  4. Redactar la descripcion. Seguir esta estructura estandarizada
  5. Asignar labels. Etiquetar la PR segun el tipo de cambio (bug, feature, refactor, docs) y la prioridad si aplica. Usar gh pr edit…
  6. Enlazar issues. Si la PR resuelve un issue, incluir Closes #XX en la descripcion para que GitHub lo cierre automaticamente al hacer merge.
  7. Asignar reviewers. Seleccionar revisores relevantes segun el area del codigo afectada. Usar gh pr create --reviewer usuario1,usuario2 o gh…
  8. Crear la PR. Ejecutar gh pr create con titulo, descripcion, labels y reviewers. Verificar que la PR aparece correctamente en GitHub y que…
  9. Revisar el resultado. Comprobar que la descripcion se renderiza bien, que los enlaces a issues funcionan y que los reviewers han sido…

What it can do on your machine

Read from SKILL.md and the folder at commit be0b51e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

PR Workflow loads about 777 tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 398 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~19
When it runs · the whole SKILL.md, loaded when a task matches
~777

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from 686f6c61/alfred-dev at commit be0b51e, republished under its MIT licence (© 686f6c61). 398 words, ~777 tokens.

Download SKILL.mdSave it as .claude/skills/pr-workflow/SKILL.md (or your agent's skills folder).
name
pr-workflow
description
Crear pull requests completas con descripcion, labels y reviewers
disable-model-invocation
true

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

  1. 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.

  2. 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.

  3. 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
  4. Redactar la descripcion. Seguir esta estructura estandarizada:

    markdown
    ## 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]
  5. 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.

  6. Enlazar issues. Si la PR resuelve un issue, incluir Closes #XX en la descripcion para que GitHub lo cierre automaticamente al hacer merge.

  7. Asignar reviewers. Seleccionar revisores relevantes segun el area del codigo afectada. Usar gh pr create --reviewer usuario1,usuario2 o gh pr edit --add-reviewer si la PR ya existe.

  8. Crear la PR. Ejecutar gh pr create con titulo, descripcion, labels y reviewers. Verificar que la PR aparece correctamente en GitHub y que los checks de CI arrancan.

  9. Revisar el resultado. Comprobar que la descripcion se renderiza bien, que los enlaces a issues funcionan y que los reviewers han sido notificados.

Show full SKILL.md (54 more words)Show less

Que NO hacer

  • No incluir lineas Co-Authored-By ni menciones a asistentes o herramientas de IA en la PR.
  • No crear PRs sin descripcion: el titulo no es suficiente para comunicar el contexto.
  • No asignar reviewers de forma indiscriminada; elegir a quienes conocen el area afectada.
  • No mezclar cambios no relacionados en la misma PR.

© 686f6c61, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/pr-workflow of 686f6c61/alfred-dev.

Open the folder on GitHubat commit be0b51e

Compare with similar skills

PR Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

PR Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PR Workflow this skill686f6c61/alfred-dev117—~777Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Understand Diff AnalysisEgonex-AI/Understand-Anything86k1 repos~1.4kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

More from 686f6c61/alfred-dev

All 11 skills in this repo
  • Incident Response

    686f6c61/alfred-dev

    Protocolo de respuesta ante incidentes en produccion: triaje, mitigacion, causa raiz y postmortem.

    117 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Memory

    686f6c61/alfred-dev

    This skill should be used when the user asks to record a design decision, search past project decisions, inspect the Alfred memory timeline, or work with the alfred-memory MCP server.

    117 GitHub stars~601 tokensUpdated 1 mo ago
    Auto-check passed
  • Sonarqube

    686f6c61/alfred-dev

    Levantar SonarQube con Docker, analizar el código y proponer mejoras.

    117 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check: notes
  • Style Direction

    686f6c61/alfred-dev

    Abrir y operar el companion visual de Selina para elegir una direccion de estilo en proyectos con interfaz.

    117 GitHub stars~2.5k tokensUpdated 1 mo ago
    Auto-check passed
  • Sync Project Docs

    686f6c61/alfred-dev

    Usar para sincronizar la documentación viva del proyecto después de una fase.

    117 GitHub stars~382 tokensUpdated 1 mo ago
    Auto-check passed
  • Write Adr

    686f6c61/alfred-dev

    Usar para escribir o cerrar un Architecture Decision Record.

    117 GitHub stars~421 tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about PR Workflow

What does PR Workflow do?

Crear pull requests completas con descripcion, labels y reviewers. PR Workflow is an agent skill from 686f6c61/alfred-dev.

When should I use PR Workflow?

PR Workflow fits situations like: tasks that involve Pull requests.

How do I install PR Workflow in Claude Code?

Run `npx skills add 686f6c61/alfred-dev --skill pr-workflow -a claude-code`. Or copy the skill folder (skills/pr-workflow in 686f6c61/alfred-dev) into .claude/skills/pr-workflow in your project. Claude Code loads it when a task matches its description.

How do I install PR Workflow in Codex?

Run `npx skills add 686f6c61/alfred-dev --skill pr-workflow -a codex`. Or copy the skill folder (skills/pr-workflow in 686f6c61/alfred-dev) into .agents/skills/pr-workflow in your project. Codex loads it when a task matches its description.

Can I use PR Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add 686f6c61/alfred-dev --skill pr-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-workflow, .gemini/skills/pr-workflow, .github/skills/pr-workflow and .opencode/skills/pr-workflow in your project.

What does PR Workflow need to run?

Going by SKILL.md and its folder, PR Workflow needs the command-line tools its instructions call (gh and git).

Does PR Workflow access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is PR Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does PR Workflow use?

PR Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does PR Workflow use?

About 777 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to PR Workflow?

Skills that share tags, products or a category with PR Workflow: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR Workflow?

686f6c61 (a GitHub user) maintains it in 686f6c61/alfred-dev, which has 117 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on August 15, 2026.

Source: 686f6c61/alfred-dev on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.