Run any Skill in Manus with one click

open-pull-request

Stars4

Forks2

UpdatedApril 14, 2026 at 07:14

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

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

torrust

torrust/torrust-tracker-deployer

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

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

More from this repository

same repository

release-new-version

torrust/torrust-tracker-deployer

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-144

run-local-e2e-test

torrust/torrust-tracker-deployer

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-144

check-system-dependencies

torrust/torrust-tracker-deployer

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-144

install-system-dependencies

torrust/torrust-tracker-deployer

Install the system dependencies required by the deployer (OpenTofu, Ansible, LXD, cargo-machete) using the built-in dependency-installer. This is the setup/installer step before using the deployer for the first time. Triggers on "install dependencies", "install system dependencies", "setup deployer", "first time setup", "missing dependency", "install opentofu", "install ansible", "install lxd", or "deployer setup".

2026-04-144

update-dependencies

torrust/torrust-tracker-deployer

Guide for updating project dependencies using the update-dependencies.sh automation script. Automates the cargo update workflow including branch creation, commit, push, and optional PR creation. Use when updating dependencies, running cargo update, or automating the dependency lifecycle. Triggers on "update dependencies", "cargo update", "update deps", "bump dependencies", or "run dependency update".

2026-04-134

commit-changes

torrust/torrust-tracker-deployer

Guide for committing changes in the torrust-tracker-deployer project. Covers conventional commit format, pre-commit verification checks, issue number conventions, and commit quality guidelines. Use when committing code, running pre-commit checks, or following project commit standards. Triggers on "commit", "commit changes", "how to commit", "pre-commit", "commit message", "commit format", or "conventional commits".

2026-04-134

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