ywc-create-pr

Name: ywc-create-pr
Availability: InStock
Author: yongwoon

Automate Git feature branch commits, security validation, and draft pull request creation.

8|1|Updated May 13, 2026

Search Tags:#automation #git #workflow #pull request #security #ci

Ready to run

npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-create-pr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ywc-create-pr
Source: https://github.com/yongwoon/ywc-agent-toolkit/tree/main/claude-code/skills/ywc-create-pr
Command: npx skills add https://github.com/yongwoon/ywc-agent-toolkit --skill ywc-create-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, bash, git, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the final stages of the development lifecycle by automating the repetitive tasks of committing changes, running pre-push validations, and creating draft pull requests, ensuring consistent team standards.

Core Features & Use Cases

Automated PR Lifecycle: Detects base branches, runs security scans, executes local CI checks, and creates draft PRs based on repository templates.
Safety & Quality Gates: Enforces mandatory self-reviews and secret scanning to prevent scope creep, debug residue, and credential leaks before code is shared.
Use Case: After finishing a feature branch, use this Skill to automatically run your project's linting and testing, verify no secrets are exposed, and open a draft PR that follows your team's specific pull request template.

Quick Start

Use the ywc-create-pr skill to commit my changes and open a draft pull request for this feature branch.

Frequently Asked Questions about ywc-create-pr

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

FAQPage Schema

How do I automate pull request creation from a Git feature branch?▼

To automate pull request creation, you can use a workflow that commits changes, runs security scans, and opens a draft PR. This process requires the GitHub CLI to analyze your feature branch and synchronize the remote pull request automatically.

What is pre-push CI verification and secret scanning for pull requests?▼

Pre-push CI verification runs local linting and testing, while secret scanning checks for exposed credentials before code is shared. These safety gates enforce mandatory self-reviews to prevent scope creep, debug residue, and credential leaks.

Do I need the GitHub CLI to automate draft PR creation and security validation?▼

Yes, you need the GitHub CLI installed locally to automate draft PR creation. The workflow also requires bash, git, and jq dependencies to perform branch analysis, execute local CI checks, and synchronize remote pull requests.

What's the best way to ensure repository-specific PR templates are used when opening a draft pull request?▼

The best way to ensure repository-specific PR templates are used is by automating the pull request lifecycle. This workflow detects your base branch and generates the draft PR directly based on your team's existing template.

Why does automated pull request creation enforce a mandatory self-review?▼

Automated pull request creation enforces a mandatory self-review to prevent scope creep and debug residue. This safety gate ensures you verify your own changes before sharing the code, maintaining consistent quality standards.

Can I run local CI checks before creating a draft pull request?▼

Yes, you can run local CI checks before creating a draft pull request. The automated workflow executes your project's linting and testing as pre-push validations, ensuring code quality before opening the draft PR.