pr-develop

Create a GitFlow-compliant draft PR to develop from feature, fix, chore, or refactor branches.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/lety-ai/lety-skill-hub --skill pr-develop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-develop
Source: https://github.com/lety-ai/lety-skill-hub/tree/main/plugins/pr-develop/skills/pr-develop
Command: npx skills add https://github.com/lety-ai/lety-skill-hub --skill pr-develop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically creates a GitFlow-compliant PR from your current working branch to develop, enforcing conventional commits and branch flow.

Core Features & Use Cases

  • Validates branch context against protected branches and GitFlow rules.
  • Generates a draft PR to develop from feature/, fix/, chore/, or refactor/ branches with Conventional Commits guidance.
  • Enforces the GitFlow release pattern and versioning policy in PR naming and flow.

Quick Start

Invoke the pr-develop skill on a working branch to open a GitFlow-compliant PR to develop following Conventional Commits rules.

Frequently Asked Questions about pr-develop

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

FAQPage Schema
How do I create a GitFlow pull request to develop using conventional commits?

To create a GitFlow pull request to develop using conventional commits, invoke the skill on your current working branch. It validates branch names, analyzes staged commits, drafts the PR via gh, and creates the final PR to develop while enforcing versioning policy.

What GitFlow branch prefixes are supported for opening a PR to develop?

Supported GitFlow branch prefixes for opening a PR to develop include feature/*, fix/*, chore/*, and refactor/*. The skill validates your current branch against these GitFlow rules and prevents PR creation from protected branches.

Can I automate PR creation from a feature branch to develop without manual drafting?

Yes, you can automate PR creation from a feature branch to develop without manual drafting. The skill analyzes staged commits, generates a draft PR with conventional commits guidance, and executes final PR creation to the develop branch automatically.

Why does my GitFlow PR to develop fail validation on protected branches?

Your GitFlow PR to develop fails validation on protected branches because the skill implements operational guardrails to prevent direct PRs from them. It enforces GitFlow rules, ensuring PRs only originate from valid feature, fix, chore, or refactor branches.

Does the PR creation process enforce conventional commits and versioning policy?

Yes, the PR creation process enforces conventional commits and versioning policy. It applies change analysis to staged commits and documents the versioning policy within the PR drafting and creation flow to maintain GitFlow release pattern compliance.

What is the best way to manage GitFlow PRs to develop with branch naming validation?

The best way to manage GitFlow PRs to develop with branch naming validation is to use an automated skill that checks branch context against GitFlow rules, applies conventional commits guidance, and uses gh to draft and create the final PR.