pr

Automate pull request workflows from branch creation to PR closure.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual PR workflows are error-prone and slow; this skill standardizes branch creation, commits, pushes, and PR creation to accelerate safe shipping.

Core Features & Use Cases

  • Automated branch creation from main with descriptive, kebab-case names.
  • Enforced commit messages following conventional commits and scope.
  • Automated PR creation with CI checks, PR URL reporting, and deployment notes.
  • Use Case: When implementing a new feature, run the PR flow to ensure code review and validation before merge.

Quick Start

Use the PR workflow to create a feature branch, commit changes, push, and open a PR.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate the end-to-end pull request workflow from branch creation to PR closure?

Automating the end-to-end pull request workflow requires standardizing branch creation from main, enforcing conventional commits, and pushing to open a PR with CI checks. This skill automates that entire sequence to accelerate safe shipping and ensure deterministic validation before merge.

What is the best way to enforce conventional commits and kebab-case branch naming in Git?

Enforcing conventional commits and kebab-case branch naming in Git requires an automated workflow that validates messages and generates descriptive branch names. This skill standardizes these formatting rules automatically, eliminating manual errors and ensuring consistent commit history across feature branches.

Can I use GitHub CLI and CI pipelines to automate PR creation with validation checks?

Using GitHub CLI and CI pipelines to automate PR creation with validation checks is fully supported. The skill leverages these tools to open pull requests, report PR URLs, and verify CI pipelines, ensuring code review and automated validation run seamlessly before deployment.

Does this automated PR workflow apply to software development teams using CI pipelines for feature work?

This automated PR workflow applies directly to software development teams using CI pipelines for feature work. It standardizes the pull request process for code reviews and automated validation, satisfying requirements for deterministic branching, conventional commits, PR templating, and CI verification.

Why does manual pull request workflow slow down feature development?

Manual pull request workflows slow down feature development because they are error-prone and require repetitive steps like branch naming, commit formatting, and PR templating. Standardizing this process with an automated flow reduces friction and accelerates safe shipping.

Do I need to manually add deployment notes when creating a PR with CI checks?

You do not need to manually add deployment notes when creating a PR with CI checks. The automated workflow handles PR creation by reporting the PR URL and including deployment notes automatically, ensuring all necessary context is provided for code review.