gh-cli
Skill0 starsChanged 4 days agoMITView on GitHub
Automatización de flujos de GitHub con gh CLI y scripts: Pull Requests con Conventional Commits, emojis y labels verificados, diagnóstico de GitHub Actions, issues y releases con notas generadas. Úsala al crear o revisar PRs, depurar workflows fallidos o publicar releases.
- Deletes or force-pushes
- Commits and pushes
32 other projects use a version of this.
Adopted by
Most recently taken up by
- KPISTOLAS/claude-skillstheir own version, first seen Nov 16, 2026
- contactandrewchl-wq/turtle-mcptheir own version, first seen Nov 15, 2026
- Pamir-AI/skillstheir own version, first seen Nov 8, 2026
- devantler-tech/ksailtheir own version, first seen Nov 7, 2026
- zlliang/skillstheir own version, first seen Nov 2, 2026
- oubakiou/skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use glab-cli, agent-browser and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
DataKnifeAISkillglab-cli
Uses the GitLab CLI (`glab`) for merge requests, issues, CI/CD, releases, and GitLab API access from the terminal. Apply when the remote is GitLab (GitLab.com or self-managed) or when the user mentions MRs, pipelines, or GitLab projects.
Also in 3 projects that use this
VercelSkillagent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
Also in 5 projects that use this
VercelSkillweb-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
Also in 5 projects that use this
MicrosoftSkillgit-commit
Stage user-selected paths, confirm the exact staged set, and create one local Conventional Commit, or generate a commit message for staged changes without committing. Use when you want a guarded commit or a ready-to-paste message.
Also in 3 projects that use this
AnthropicSkillpdf
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
Also in 6 projects that use this
OpenAISkillusing-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Also in 3 projects that use this
Other versions32 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 32
- mfts/papermark★ 9.2ksame name
- papermark/papermark★ 9.2ksame name
- farm-fe/farm★ 5.6ksame name
- PierreBeucher/cloudypad★ 980same name
- devantler-tech/ksail★ 164same name
- yamcodes/arkenv★ 151same name
- ericmjl/skills★ 42same name
- jaskirat1616/grok-skills★ 22same name
- JamesPrial/github-skills★ 18same name
- HK-hub/AgentSkills★ 6same name
22 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- git-cleanupSkill
- skill-creatorSkill
- astro-architectureSkill
- monorepo-architectureSkill
- nestjs-architectureSkill
- nextjs-architectureSkill
- react-native-architectureSkill
- git-cleanupSkill
- backend-best-practicesSkill
- clean-codeSkill
- code-quality-reviewSkill
- design-patternsSkill
- frontend-best-practicesSkill
- solid-principlesSkill
- tdd-workflowSkill
- ssh-connectSkill
- ts-import-organizerSkill
- idd-applySkill
- idd-exploreSkill
- idd-planSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
No aplica a repositorios de GitLab.
“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
🐙 GitHub CLI (gh) Workflow & Automation
🎯 Propósito
Guiar al asistente en la gestión de repositorios de GitHub con gh CLI y scripts auxiliares. Estandariza la creación de Pull Requests (Conventional Commits, emoji por tipo, scope solo con issue, labels que ya existen en el repo), el diagnóstico de GitHub Actions fallidos, el trabajo con issues y la publicación de releases con notas generadas por GitHub.
⚡ Cuándo Activar esta Skill
- Al trabajar en repositorios alojados en GitHub (
github.como GitHub Enterprise). - Al crear, revisar, aprobar o fusionar Pull Requests (
gh proscripts/create_pr.sh). - Al diagnosticar workflows o checks fallidos de GitHub Actions (
gh run,gh pr checksoscripts/diagnose_run.sh). - Al crear, listar o comentar issues, o al publicar releases y tags.
- No aplica a repositorios de GitLab.
📋 Flujo de Trabajo Paso a Paso
flowchart TD
A["Verificar Entorno\n(scripts/check_env.sh)"] --> B{"Tarea Requerida"}
B -->|"Crear Pull Request"| C["scripts/create_pr.sh --dry-run\n→ confirmar → sin --dry-run"]
B -->|"Depurar Actions"| D["scripts/diagnose_run.sh\n(gh run view --log-failed)"]
B -->|"Issues"| E["gh issue list/view/create/comment"]
B -->|"Releases"| F["scripts/release_helper.sh\n(gh release create --generate-notes)"]- Paso 1: Verificación de Estado y Autenticación:
Si falla la autenticación, pide al usuario que ejecutebash <skill-dir>/scripts/check_env.shgh auth login; nunca pidas ni escribas tokens. - Paso 2: Creación Estandarizada de Pull Requests:
- Previsualiza siempre primero y muestra al usuario título, labels y rama base:
# Issue detectado de la rama (feat/42-login-form) o explícito: bash <skill-dir>/scripts/create_pr.sh --issue 42 --domain auth --dry-run # Sin issue (título sin scope: <type>: <emoji> <desc>): bash <skill-dir>/scripts/create_pr.sh --dry-run - Tras la confirmación, repite el comando sin
--dry-run. Añade--pushsolo si la rama no está publicada y el usuario lo aprueba;--draftsi el trabajo no está listo. - Alternativa manual:
gh pr create --title "<título>" --body "<cuerpo>" --base main.
- Previsualiza siempre primero y muestra al usuario título, labels y rama base:
- Paso 3: Revisión y Fusión de PRs:
gh pr view <n> --comments # contexto y conversación gh pr diff <n> # cambios gh pr checks <n> # estado de CI gh pr review <n> --approve # o --request-changes --body "..." gh pr merge <n> --squash --delete-branch # solo con aprobación explícita del usuario - Paso 4: Diagnóstico de GitHub Actions:
Lee el log, identifica la causa y corrige el código. Reintenta (# Último run fallido de la rama actual, solo logs de pasos fallidos: bash <skill-dir>/scripts/diagnose_run.sh # Checks de un PR y logs de un job concreto: bash <skill-dir>/scripts/diagnose_run.sh --pr 57 --job lint --lines 50gh run rerun <id> --failed) solo si el fallo es transitorio (red, runner caído). - Paso 5: Issues y Releases:
gh issue list --assignee @me --state open gh issue view 42 --comments bash <skill-dir>/scripts/release_helper.sh draft-notes bash <skill-dir>/scripts/release_helper.sh create v1.4.0 --dry-run
🛠️ Scripts y Herramientas Auxiliares
Rutas:
<skill-dir>es el directorio que contiene esteSKILL.md(p. ej..claude/skills/<name>/o.agents/skills/<name>/). Ejecuta los scripts desde la raíz del proyecto del usuario, no desde<skill-dir>.
scripts/check_env.sh: Validagit,gh, la sesión activa y el repositorio de GitHub detrás deorigin.scripts/create_pr.sh: Crea el PR con:- Título con issue:
<type>(#<issue-id>): <emoji> <description>; sin issue:<type>: <emoji> <description>. - Label de tipo con los labels por defecto de GitHub (
enhancement,bug,documentation) ydomain: <nombre>opcional. - Dominios permitidos: si existe
.gh-domainsen la raíz del repo (uno por línea),--domaindebe estar en esa lista. - Verificación previa de que todos los labels existen, de que no hay ya un PR abierto para la rama y de que la rama tiene upstream.
- Cuerpo con
Closes #<id>, resumen de commits y la plantilla.github/pull_request_template.mdsi existe.
- Título con issue:
scripts/diagnose_run.sh: Último run fallido de la rama o PR y logs de los pasos fallidos, filtrables por job.scripts/release_helper.sh:list,view,draft-notesycreate <tag>con validación SemVer y notas generadas por GitHub.
⚠️ Reglas Críticas
- Regla de Título y Scope del PR:
- Con issue:
<type>(#<issue-id>): <emoji> <description>(ej.feat(#42): ✨ login form). - Sin issue:
<type>: <emoji> <description>(ej.chore: 🔧 upgrade dependencies). - NUNCA usar carpetas, paquetes ni apps como scope (
feat(web): ...está PROHIBIDO).
- Con issue:
- Labels existentes, nunca inventados:
- Usa solo labels que ya existen en el repositorio (
gh label list). No ejecutesgh label createsin permiso explícito del usuario. - Los dominios válidos son los de
.gh-domains; nunca inventes uno.
- Usa solo labels que ya existen en el repositorio (
- Acciones con efectos externos requieren confirmación:
- Crear o fusionar PRs, aprobar, cerrar issues, publicar releases, relanzar workflows o hacer push: muestra primero lo que se hará (
--dry-run) y espera confirmación. - PROHIBIDO
git push --forcehacia ramas compartidas,gh pr merge --adminpara saltarse protecciones ygh repo delete.
- Crear o fusionar PRs, aprobar, cerrar issues, publicar releases, relanzar workflows o hacer push: muestra primero lo que se hará (
- No interactividad: Pasa siempre
--title/--body(o--fill) y flags explícitos; nunca dejesghesperando un prompt. - Credenciales: Nunca imprimas, pidas ni guardes tokens (
GH_TOKEN,gh auth token). La autenticación la hace el usuario congh auth login. - Salida estructurada: Para leer datos usa
--json <campos> --jq <filtro>en lugar de parsear texto formateado.
📚 Referencias Adicionales
- Estándares de GitHub: títulos, emojis, labels y cuerpo del PR
- CheatSheet de comandos gh
- GitHub Actions y resolución de problemas
- Ejemplos de flujos de trabajo
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

