pr-create

Creates pull requests in Azure DevOps or GitHub with compliance, secrets, and findings gates.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill pr-create-vickysrawat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-create
Source: https://github.com/vickysrawat/AI-Assisted-development/tree/main/skills/pr-create
Command: npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill pr-create-vickysrawat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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

Frequently Asked Questions about pr-create

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a pull request in Azure DevOps from the command line?

Run the pr-create skill after generating a description with pr-describe. It detects the Azure DevOps remote, resolves your AZURE_DEVOPS_PAT credential, runs compliance and secrets gates, and submits the PR via the ADO REST API with the work item linked.

Can I create a GitHub pull request with a linked Azure DevOps work item?

Yes. The skill detects a GitHub remote and submits via the GitHub REST API or gh CLI. The ADO work item ID stays as a textual reference in the title and body, since GitHub has no native ADO work-item linkage.

What happens if the secrets scan finds a credential in my diff?

PR creation stops immediately. The secrets gate is hard and non-skippable — no override flag exists, because a pushed credential is irreversible. You must remove the secret from the branch before re-running.

Does pr-create work offline or without a connection?

Yes. Use the --offline flag with --release and --sprint IDs to skip the connection prompt. The skill writes a complete PR draft artifact with a pre-filled submit URL to docs/Release<R>/Sprint<S>/ for manual submission.

Why does pr-create say no pr-describe output was found?

The skill requires an ICEA-validated PR description generated by pr-describe in the same conversation. Run /pr-describe first, then re-run /pr-create — unvalidated descriptions are never submitted.

What git remote providers are supported for direct PR submission?

Azure DevOps and GitHub are supported for direct API submission. If the remote provider is detected as anything else, the skill forces the draft path and produces a manual-submission artifact instead.