What problem does it solve? Creating a pull request manually means remembering to run quality checks, code reviews, and coverage verification first, then figuring out the right CLI for your git platform and writing a good title and description. This Skill automates that entire flow so a PR is only ever opened after the required gates pass. ## Core Features & Use Cases - Two PR modes: implementation PRs (feature/fix/chore branches into an integration branch) and promotion PRs (develop into master/main/release), each with the appropriate set of blocking quality gates. - Mandatory quality gates: runs quality-check, code-review, and coverage-verify for implementation PRs (quality-check only for promotions), plus an optional Definition of Done check, and blocks the PR if any gate fails. - Platform auto-detection: detects GitHub, GitLab, Bitbucket, Gitea, or Azure Repos from the git remote and uses the matching CLI (gh, glab, tea, az repos) to create the PR with a generated title and description. - Use Case: You finished a feature branch and say "crea el PR". The Skill commits pending changes via git-commit, runs all quality gates, archives the completed user story spec, pushes the branch, and opens the PR on the detected platform. ## Quick Start Ask the agent to create a pull request from your current branch to develop, for example: create the PR for this feature branch.