pr

Create structured pull requests for the openwop repository with compliance checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manages the creation of well-structured pull requests, detects lane type, enforces code conventions, and provides necessary pre-flight checks.

Core Features & Use Cases

  • Lane Detection: Automatically determines the type of pull request based on affected code areas.
  • Conventional Commit Checking: Ensures DCO, Conventional Commits, CHANGELOG, and openwop:check compliance.
  • PR Generation: Outputs a pull request template with title and body pre-filled for review.

Quick Start

Run 'pr' to generate a structured pull request based on your current branch changes.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I create a pull request with conventional commits and DCO compliance?

To create a compliant pull request, you can use an automated tool that analyzes your Git commits for DCO and Conventional Commits compliance. It then generates a structured PR body and title based on the modified files.

How does lane detection work for pull requests?

Lane detection works by analyzing the modified files in your current Git branch to automatically determine the specific type or category of the pull request based on the affected code areas.

Do I need Git and GitHub installed to generate a structured pull request body?

Yes, you need Git for commit analysis and GitHub for pull request creation. The tool uses these dependencies to analyze branch changes and output a pre-filled template for review.

What is the best way to automate code checks for DCO and Conventional Commits?

The best way to automate these code checks is by running a pre-flight script that performs code analysis on your current branch. It enforces DCO, Conventional Commits, and CHANGELOG compliance before generating the PR.

Why does my pull request fail code convention checks before submission?

Your pull request may fail code convention checks if your commits lack DCO sign-off or do not follow Conventional Commits standards. Running a pre-flight compliance check identifies these specific formatting issues.