What problem does it solve? Submitting a pull request manually means re-checking compliance, scanning for leaked secrets, reviewing open findings, and formatting the description every time. This Skill automates PR submission to Azure DevOps or GitHub while enforcing ICEA compliance, secrets scanning, and findings gates before anything is created. ## Core Features & Use Cases - Provider auto-detection: Detects whether the git remote is Azure DevOps or GitHub and uses the correct REST API, authentication method, and base-branch policy for each. - Mandatory quality gates: Runs an ICEA compliance check (via pr-spec-review), a non-skippable secrets scan on the branch diff, and an open-findings ledger check before any PR is submitted or drafted. - Offline draft fallback: When offline, when the remote is unreachable, or when the developer declines to connect, writes a complete PR draft artifact with a pre-filled submit URL to docs/Release<R>/Sprint<S>/. - Use Case: A developer finishes a feature branch, runs /pr-describe to generate a validated description, then runs /pr-create to submit the PR to Azure DevOps with the work item linked and all gates verified. ## Quick Start Ask the assistant to create a pull request for the current branch after running pr-describe, for example by saying "create a PR for this branch in Azure DevOps".