PluginBench
Skill
Pass
Audit score 90

create-pr

neolabhq/context-engineering-kit

How to install create-pr

npx skills add https://github.com/neolabhq/context-engineering-kit --skill create-pr
Claude Code
Cursor
Windsurf
Cline
Full instructions (SKILL.md)

Source of truth, from neolabhq/context-engineering-kit.


name: create-pr description: Create pull requests using GitHub CLI with proper templates and formatting argument-hint: None required - interactive guide for PR creation allowed-tools: Bash(gh pr:), Bash(gh auth:), Bash(git status:), Bash(git push:), Bash(git branch:*), Skill(git:commit)

How to Create a Pull Request Using GitHub CLI

This guide explains how to create pull requests using GitHub CLI in our project.

Important: All PR titles and descriptions should be written in English.

Prerequisites

Check if gh is installed, if not follow this instruction to install it:

  1. Install GitHub CLI if you haven't already:

    # macOS
    brew install gh
    
    # Windows
    winget install --id GitHub.cli
    
    # Linux
    # Follow instructions at https://github.com/cli/cli/blob/trunk/docs/install_linux.md
    
  2. Authenticate with GitHub:

    gh auth login
    

Pre-flight Checks

Before creating a PR, check for uncommitted changes:

  1. Run git status to check for uncommitted changes (staged, unstaged, or untracked files)
  2. If uncommitted changes exist, use the Skill tool to run the commit skill first:
    Skill: commit
    
  3. This ensures all your work is committed before creating the PR

Creating a New Pull Request

  1. First, prepare your PR description following the template in @.github/pull_request_template.md

  2. Use the gh pr create --draft command to create a new pull request:

    # Basic command structure
    gh pr create --draft --title "✨(scope): Your descriptive title" --body "Your PR description" --base main 
    

    For more complex PR descriptions with proper formatting, use the --body-file option with the exact PR template structure:

    # Create PR with proper template structure
    gh pr create --draft --title "✨(scope): Your descriptive title" --body-file .github/pull_request_template.md --base main
    

Best Practices

  1. Language: Always use English for PR titles and descriptions

  2. PR Title Format: Use conventional commit format with emojis

    • Always include an appropriate emoji at the beginning of the title
    • Use the actual emoji character (not the code representation like :sparkles:)
    • Examples:
      • ✨(supabase): Add staging remote configuration
      • 🐛(auth): Fix login redirect issue
      • 📝(readme): Update installation instructions
  3. Description Template: Always use our PR template structure from @.github/pull_request_template.md:

  4. Template Accuracy: Ensure your PR description precisely follows the template structure:

    • Don't modify or rename the PR-Agent sections (pr_agent:summary and pr_agent:walkthrough)
    • Keep all section headers exactly as they appear in the template
    • Don't add custom sections that aren't in the template
  5. Draft PRs: Start as draft when the work is in progress

    • Use --draft flag in the command
    • Convert to ready for review when complete using gh pr ready

Common Mistakes to Avoid

  1. Using Non-English Text: All PR content must be in English
  2. Incorrect Section Headers: Always use the exact section headers from the template
  3. Adding Custom Sections: Stick to the sections defined in the template
  4. Using Outdated Templates: Always refer to the current @.github/pull_request_template.md file

Missing Sections

Always include all template sections, even if some are marked as "N/A" or "None"

Additional GitHub CLI PR Commands

Here are some additional useful GitHub CLI commands for managing PRs:

# List your open pull requests
gh pr list --author "@me"

# Check PR status
gh pr status

# View a specific PR
gh pr view <PR-NUMBER>

# Check out a PR branch locally
gh pr checkout <PR-NUMBER>

# Convert a draft PR to ready for review
gh pr ready <PR-NUMBER>

# Add reviewers to a PR
gh pr edit <PR-NUMBER> --add-reviewer username1,username2

# Merge a PR
gh pr merge <PR-NUMBER> --squash

Using Templates for PR Creation

To simplify PR creation with consistent descriptions, you can create a template file:

  1. Create a file named pr-template.md with your PR template
  2. Use it when creating PRs:
gh pr create --draft --title "feat(scope): Your title" --body-file pr-template.md --base main

Related Documentation

Related skills

More from neolabhq/context-engineering-kit and the wider catalog.

PR

prompt-engineering

neolabhq/context-engineering-kit

Use this skill when you writing commands, hooks, skills for Agent, or prompts for sub agents or any other LLM interaction, including optimizing prompts, improving LLM outputs, or designing production prompt templates.

834 installsAudited
CO

context-engineering

neolabhq/context-engineering-kit

Understand the components, mechanics, and constraints of context in agent systems. Use when writing, editing, or optimizing commands, skills, or sub-agents prompts.

823 installs
TH

thought-based-reasoning

neolabhq/context-engineering-kit

Use when tackling complex reasoning tasks requiring step-by-step logic, multi-step arithmetic, commonsense reasoning, symbolic manipulation, or problems where simple prompting fails - provides comprehensive guide to Chain-of-Thought and related prompting techniques (Zero-shot CoT, Self-Consistency, Tree of Thoughts, Least-to-Most, ReAct, PAL, Reflexion) with templates, decision matrices, and research-backed patterns

810 installs
RE

reflect

neolabhq/context-engineering-kit

Reflect on previus response and output, based on Self-refinement framework for iterative improvement with complexity triage and verification

795 installsAudited
UP

update-docs

neolabhq/context-engineering-kit

Update and maintain project documentation for local code changes using multi-agent workflow with tech-writer agents. Covers docs/, READMEs, JSDoc, and API documentation.

785 installsAudited
MU

multi-agent-patterns

neolabhq/context-engineering-kit

Design multi-agent architectures for complex tasks. Use when single-agent context limits are exceeded, when tasks decompose naturally into subtasks, or when specializing agents improves quality.

779 installsAudited