create-pr

Run quality checks on a feature branch and open a GitHub PR when checks pass.

97|4|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/go-to-k/cdkd --skill create-pr-go-to-k
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/go-to-k/cdkd/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/go-to-k/cdkd --skill create-pr-go-to-k

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end GitHub PR workflow by running quality checks, validating branches, and opening a PR when checks pass, saving time and preventing manual errors.

Core Features & Use Cases

  • Run quality checks (lint, tests, CI, docs consistency) on a feature branch.
  • Create a GitHub PR with a coherent title and body based on the diff.
  • Guardrails to prevent PR creation on main and to ensure proper branch flow.

Quick Start

Follow the prompts to verify and create a PR from your feature branch.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate GitHub PR creation after CI and lint checks pass?

Automate GitHub PR creation by running quality checks on a feature branch first; the workflow opens a PR with a drafted body and title only when all lint, test, and CI validations succeed.

What is the best way to generate a PR body from a branch diff automatically?

Generating a PR body from a diff automatically involves analyzing branch changes to construct a coherent title and description, ensuring PR metadata reflects the validated code updates.

Can I prevent PR creation on the main branch during feature branch workflows?

Yes, you can prevent PR creation on the main branch by using guardrails that enforce proper branch flow, ensuring PRs are only opened from valid feature branches after checks pass.

Does this PR workflow automation handle docs consistency checks as well?

Yes, this PR workflow automation handles docs consistency checks alongside lint, tests, and CI, ensuring comprehensive code quality validation before opening the final GitHub PR.

How do I select the correct PR base branch when automating feature branch workflows?

Selecting the correct PR base branch during automation ensures the feature branch targets the appropriate integration point, validating branch flow before constructing and submitting the GitHub PR.