skills.rest
TabooLib
TabooLibOFFICIAL
Explore all skills by this author →
GitHub

create-pr

Create a GitHub issue and planning branch from collected feature requirements.

388|118|Updated Feb 6, 2018
Search Tags:#automation#workflow#planning#github#branch#issue#create-pr
One-click install
npx skills add https://github.com/TabooLib/taboolib --skill create-pr-taboolib
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/TabooLib/taboolib/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/TabooLib/taboolib --skill create-pr-taboolib

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end patch creation by collecting requirements, opening an issue in the main repository, and establishing a local feature branch for planning.

Core Features & Use Cases

  • Collects requirements via guided questions and consolidates them into a structured patch request.
  • Creates an issue in the primary repository TabooLib/taboolib with a formatted title and body.
  • Generates a local feature branch named using a standardized pattern and switches to planning mode for detailed analysis.

Quick Start

Invoke the create-pr skill to initiate a new patch workflow.

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 issue creation and branch setup for feature planning?▼

Automating GitHub issue creation and branch setup involves collecting feature requirements, creating an issue in the main repository via GitHub CLI, and switching to a local planning branch. This workflow validates inputs and applies standardized branch naming for coordinated patch development.

What is the best way to create a structured patch request from feature requirements?▼

Creating a structured patch request uses guided questions to gather and consolidate feature requirements. This process formats the collected information into a standardized issue title and body before opening it in the primary repository.

How do I start a feature development workflow with planning mode?▼

Starting a feature development workflow with planning mode requires invoking an automated patch creation process. It establishes a local feature branch using a standardized naming pattern and transitions the environment into planning mode for detailed analysis.

Does the patch creation workflow require GitHub CLI to open issues?▼

The patch creation workflow implements issue creation via GitHub CLI. It automates opening issues in the main repository by applying formatted titles and bodies generated from collected feature requirements.

What are the limitations of automating patch creation for feature development?▼

Automating patch creation is limited to feature development workflows where teams coordinate planning with local branches. It applies specifically to the primary repository and focuses on information gathering, issue creation, and branch setup rather than code implementation.

Related Skills

Explore More Software Engineering Skills→
shirulotshirulot

yeet

Automate Git staging, committing, and GitHub pull request creation.

Community
Advanced
kevinnguyen271090kevinnguyen271090
15

planning

Generate detailed technical implementation plans for software systems.

Community
Basic
dtsongdtsong
1

Git Branches

List and visualize Git branch status with remote tracking and synchronization.

Community
Intermediate
GGPromptsGGPrompts
147

merge

Merge feature branches into main and clean up worktrees using Git.

Community
Advanced