pr

Create GitHub pull requests from in-progress work with branch and commit handling.

1|2|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/kynetic-ai/kynetic-spec --skill pr-kynetic-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/kynetic-ai/kynetic-spec/tree/main/.claude/skills/pr
Command: npx skills add https://github.com/kynetic-ai/kynetic-spec --skill pr-kynetic-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create PRs from your current work, handling branch creation, commits, push, and pull-request creation, while gracefully handling branch protection and guiding you through the review workflow.

Core Features & Use Cases

  • Automated PR creation from in-progress work and completed tasks.
  • Branch strategy and protection checks when targeting main.
  • Integrated PR review flow via kspec workflows to ensure quality gates.

Quick Start

Start the PR flow for your current task using the /pr command, then follow the automated prompts to review and merge.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate GitHub pull request creation from my current branch?

Automating GitHub pull request creation from your current branch is handled by committing work, pushing changes, and generating the PR automatically with branch protection checks and guided code review workflows.

What is the best way to create a pull request while ensuring branch protection on main?

Creating a pull request while ensuring branch protection on main involves automated strategy checks that prevent direct commits and guide developers through a controlled code review and merge workflow.

Can I generate pull requests automatically from completed development tasks?

Generating pull requests automatically from completed development tasks is supported by integrating task metadata to create branches, push commits, and open PRs that reflect your in-progress work.

How does the PR workflow integrate with task and spec metadata for code review?

The PR workflow integrates with task and spec metadata for code review by applying quality gates and automated branching strategies to ensure the generated pull request matches the defined task requirements.

Do I need to manually name branches when automating pull request generation?

You do not need to manually name branches when automating pull request generation because the workflow applies automatic branch naming based on task metadata to streamline the merge process.

Why does my automated pull request workflow pause before merging to main?

An automated pull request workflow pauses before merging to main to enforce branch protection safeguards and guide developers through a structured code review process to ensure quality gates are met.