open-pull-request

Open a pull request from a feature branch using GitHub CLI (preferred) or GitHub MCP tools. Covers pre-flight checks, correct base/head configuration for fork workflows, title/body conventions, and post-creation validation. Use when asked to "open PR", "create pull request", or "submit branch for review".

Ir a la instalación

Repositorio: torrust/torrust-tracker-deployer
Última actividad en el origen: 14 de abril de 2026 a las 07:14
Idioma detectado de SKILL.md: inglés
Estrellas: 4
Forks: 2

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/torrust/torrust-tracker-deployer --skill open-pull-request

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

release-new-version

Guide for releasing a new version of the deployer using the standard branch/tag workflow. Covers version bump, signed release commit, pushing main, creating signed tag, creating release branch, and verifying Docker + crate publication workflows. Use when asked to "release", "cut a version", "publish a new version", or "create release vX.Y.Z".

2026-04-14

run-local-e2e-test

Run a complete local end-to-end test using the LXD provider to verify a feature, fix, or change works as expected from the user's perspective. Covers creating an environment config, provisioning a VM, deploying the tracker, verifying it works, and cleaning up. Use when manually testing changes, validating a new feature locally, running a full deployment smoke test, or checking that the deployer works end-to-end. Triggers on "local e2e", "manual e2e test", "test my changes locally", "run deployer end-to-end", "smoke test", "test on LXD", "verify feature works", or "full deployment test".

2026-04-14

check-system-dependencies

Check whether the system has all dependencies required by the deployer (OpenTofu, Ansible, LXD, cargo-machete). Use before running provisioning, E2E tests, or any infrastructure command. Triggers on "check dependencies", "check system dependencies", "are dependencies installed", "verify dependencies", "dependency check", or "missing tools".

2026-04-14

Ver todos los de este repositorio

name	open-pull-request
description	Open a pull request from a feature branch using GitHub CLI (preferred) or GitHub MCP tools. Covers pre-flight checks, correct base/head configuration for fork workflows, title/body conventions, and post-creation validation. Use when asked to "open PR", "create pull request", or "submit branch for review".
metadata	{"author":"torrust","version":"1.0"}

Open a Pull Request

This skill explains how to create a pull request for this repository in a repeatable way.

CLI vs MCP decision rule

Use the tool that matches the loop:

Inner loop (fast local branch work): prefer GitHub CLI (gh) because it is fast and low overhead.
Outer loop (cross-system coordination): use MCP when you need structured/authenticated access across shared systems.

For opening a PR from the current local branch, prefer gh pr create.

Pre-flight checks

Before opening a PR:

Working tree is clean (git status)
Branch is pushed to remote
Commits are signed (git log --show-signature -n 1)
Required checks have been run (./scripts/pre-commit.sh)

Title and description convention

Use conventional commit style in the PR title when possible, including issue reference.

Examples:

ci: [#448] add crate publish workflow
docs: [#448] define release process

Include in PR body:

Summary of changes
Files/workflows touched
Validation performed
Issue link (Closes #<issue-number>)

Option A (Preferred): GitHub CLI

Same-repo branch

gh pr create \
  --repo torrust/torrust-tracker-deployer \
  --base main \
  --head <branch-name> \
  --title "<title>" \
  --body "<body>"

Fork branch (common maintainer flow)

gh pr create \
  --repo torrust/torrust-tracker-deployer \
  --base main \
  --head <fork-owner>:<branch-name> \
  --title "<title>" \
  --body "<body>"

If successful, gh prints the PR URL.

Option B: GitHub MCP tools

When MCP pull request management tools are available:

Create branch remotely if needed
Open PR with base main and correct head branch
Capture and share resulting PR URL

Post-creation validation

After PR creation:

Verify PR points to torrust/torrust-tracker-deployer:main
Verify head branch is correct
Confirm CI workflows started
Confirm issue is linked in description

Troubleshooting

fatal: ... does not appear to be a git repository: push to correct remote (git remote -v)
A pull request already exists: open existing PR URL instead of creating a new one
Permission errors on upstream repo: create PR from your fork branch (owner:branch)

References

docs/contributing/commit-process.md
docs/contributing/pr-review-guide.md
Existing branch skill: .github/skills/dev/git-workflow/create-feature-branch/skill.md

open-pull-request

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Más de este repositorio

Open a Pull Request

CLI vs MCP decision rule

Pre-flight checks

Title and description convention

Option A (Preferred): GitHub CLI

Same-repo branch

Fork branch (common maintainer flow)

Option B: GitHub MCP tools

Post-creation validation

Troubleshooting

References

Open a Pull Request

CLI vs MCP decision rule

Pre-flight checks

Title and description convention

Option A (Preferred): GitHub CLI

Same-repo branch

Fork branch (common maintainer flow)

Option B: GitHub MCP tools

Post-creation validation

Troubleshooting

References