// 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".
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".
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".
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".
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".
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".
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".
| 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"} |
This skill explains how to create a pull request for this repository in a repeatable way.
Use the tool that matches the loop:
gh) because it is fast and low overhead.For opening a PR from the current local branch, prefer gh pr create.
Before opening a PR:
git status)git log --show-signature -n 1)./scripts/pre-commit.sh)Use conventional commit style in the PR title when possible, including issue reference.
Examples:
ci: [#448] add crate publish workflowdocs: [#448] define release processInclude in PR body:
Closes #<issue-number>)gh pr create \
--repo torrust/torrust-tracker-deployer \
--base main \
--head <branch-name> \
--title "<title>" \
--body "<body>"
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.
When MCP pull request management tools are available:
main and correct head branchAfter PR creation:
torrust/torrust-tracker-deployer:mainfatal: ... 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 oneowner:branch)docs/contributing/commit-process.mddocs/contributing/pr-review-guide.md.github/skills/dev/git-workflow/create-feature-branch/skill.md