pr-submitter

Name: pr-submitter
Availability: InStock
Author: Fu-Jie

Push a feature branch and create a validated GitHub Pull Request with a bilingual body.

286|24|Updated Dec 20, 2025

Search Tags:#automation #git #github #pull-request #pr-create #shell-escape

Ready to run

npx skills add https://github.com/Fu-Jie/openwebui-extensions --skill pr-submitter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-submitter
Source: https://github.com/Fu-Jie/openwebui-extensions/tree/main/.gemini/skills/pr-submitter
Command: npx skills add https://github.com/Fu-Jie/openwebui-extensions --skill pr-submitter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated, reliable PR submission by generating a shell-escape-safe, bilingual PR body and handling the final push and PR creation steps.

Core Features & Use Cases

Pre-flight checks to ensure not on a protected branch, authentication status, and commits ready for push.
Auto-generates a shell-escape-safe PR body written to a temporary file to avoid inline multi-line strings and shell expansion.
Supports bilingual (English/Chinese) PR bodies and documentation updates as part of release workflows.

Quick Start

Push your feature branch and run the pr-submitter workflow to generate a shell-safe PR body file and create the pull request.

Frequently Asked Questions about pr-submitter

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

FAQPage Schema

How do I automate GitHub pull request creation with a formatted body?▼

To automate GitHub pull request creation, you can use a workflow that pushes your feature branch and generates a validated PR body. This process writes the PR body to a temporary file to avoid shell-escaping issues and creates the pull request via the authenticated gh CLI.

Why does my automated PR body break with shell expansion issues?▼

Automated PR body generation breaks due to shell expansion when multi-line strings are passed inline. Writing the bilingual PR body to a temporary file before submission avoids shell-escaping issues and ensures the text is formatted safely.

Do I need the gh CLI to create a pull request from a feature branch?▼

Yes, you need the gh CLI to create a pull request from a feature branch. The CLI must be properly authenticated before submission, and pre-flight checks verify this authentication status along with ensuring you are not on a protected branch.

What are the prerequisites for submitting a PR from a non-main branch?▼

Prerequisites for submitting a PR from a non-main branch include having the gh CLI authenticated and ensuring all changes are committed prior to submission. The workflow applies pre-flight checks to verify the current branch is not main and commits are ready.

Can I generate a bilingual PR body for GitHub automatically?▼

Yes, you can generate a bilingual PR body for GitHub automatically. The automation supports creating English and Chinese PR bodies, writing the formatted text to a safe temporary file to handle the multi-line content without shell expansion errors.

When should I not use an automated PR submission workflow?▼

You should not use an automated PR submission workflow when you are currently on a protected branch like main, or if you have uncommitted changes. The workflow operates within a constrained scope and requires all changes to be committed prior to submission.