open-pr

Name: open-pr
Availability: InStock
Author: cookeyholder

Create a GitHub Pull Request with a Traditional Chinese PR message.

Updated Apr 9, 2026

Search Tags:#automation #workflow #gh #pull-request #open-pr #traditional-chinese

Ready to run

npx skills add https://github.com/cookeyholder/django-devcontainer-template --skill open-pr-cookeyholder

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: open-pr
Source: https://github.com/cookeyholder/django-devcontainer-template/tree/main/.agent/skills/open-pr
Command: npx skills add https://github.com/cookeyholder/django-devcontainer-template --skill open-pr-cookeyholder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automatically initiates a GitHub Pull Request from the current branch and generates a comprehensive, Traditional Chinese PR message, reducing manual drafting and ensuring consistency across reviews.

Core Features & Use Cases

Auto PR generation: Creates a PR from the active branch using gh and auto-populates a detailed Traditional Chinese PR description.
Structured messaging: Produces standardized sections (summary, changes, tests, risks) to streamline code review and release processes.
Auto-tracking: Immediately integrates with review-pr-3x to monitor reviews and CI status after PR creation.
Language consistency: Enforces Traditional Chinese terminology to avoid non-standard phrasing in PRs.

Quick Start

From the current branch, create a PR with gh and let the system generate a complete Traditional Chinese PR message.

Frequently Asked Questions about open-pr

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

FAQPage Schema

How do I automatically create a GitHub pull request with a Traditional Chinese description?▼

To create a GitHub pull request with a Traditional Chinese description, you can use this Skill to generate a PR from your active branch using the gh CLI. It automatically produces a structured PR body with summary, changes, tests, and risks sections in Traditional Chinese.

What is the best way to standardize pull request messages for localization compliance?▼

Standardizing pull request messages for localization compliance involves enforcing consistent terminology and structured sections. This Skill generates a standardized Traditional Chinese PR body, ensuring non-standard phrasing is avoided and localization requirements are met across all reviews.

Can I create a pull request from the main branch using this automation workflow?▼

No, you cannot create a pull request from the main branch using this automation workflow. The Skill explicitly validates the active branch and ensures it is not main before proceeding, preventing accidental PR creation from the default branch.

Do I need the gh CLI installed to generate a structured PR message?▼

Yes, you need the gh CLI installed to generate a structured PR message. The Skill validates gh availability before initiating the pull request creation process, relying on the GitHub CLI to create the PR from your active branch.

How does the pull request creation process integrate with ongoing review tracking?▼

The pull request creation process integrates with review tracking by automatically triggering the review-pr-3x process after PR creation. This integration monitors reviews and CI status immediately after the PR is opened from the active branch.

What sections are included in the generated Traditional Chinese PR body?▼

The generated Traditional Chinese PR body includes standardized sections for summary, changes, tests, and risks. These structured sections are produced automatically to streamline the code review and release processes.