skills.rest
JeremyDev87
JeremyDev87COMMUNITY
Explore all skills by this author →
WebsiteGitHub

pr-all-in-one

Automate PR creation and updates from commits with issue linking and multilingual descriptions.

31|3|Updated Dec 12, 2025
Search Tags:#automation#git#workflow#branching#pr#pull-request#issue-linking
One-click install
npx skills add https://github.com/JeremyDev87/codingbuddy --skill pr-all-in-one
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-all-in-one
Source: https://github.com/JeremyDev87/codingbuddy/tree/main/packages/rules/.ai-rules/skills/pr-all-in-one
Command: npx skills add https://github.com/JeremyDev87/codingbuddy --skill pr-all-in-one

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified commit and PR workflow. Auto-commits changes, creates/updates PRs with smart issue linking and multi-language support.

Core Features & Use Cases

  • Auto-commit changes, group by feature or purpose
  • Create or update PRs with smart issue linking and multilingual PR descriptions
  • Supports English, Korean, or bilingual PR language outputs and drafting

Quick Start

Provide a target-branch and an issue-id to automatically create or update a PR.

Frequently Asked Questions about pr-all-in-one

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

FAQPage Schema
How do I automate pull request creation from git commits with issue linking?▼

Automating pull request creation involves configuring a workflow that reads commit changes and generates PRs with linked issues. You need a JSON configuration file to define default branches, issue patterns, and language preferences.

How does issue linking work when automating PR workflows across branches?▼

Issue linking works by matching commit messages against a configured issue pattern. When creating or updating a PR, the workflow parses commits, extracts referenced issue IDs, and embeds these links directly into the PR description.

Can I generate pull request descriptions in multiple languages like Korean and English?▼

Yes, multilingual PR descriptions in English, Korean, or bilingual formats are supported. You control the language output through a configuration setting, enabling teams to standardize PR descriptions across different language preferences.

Do I need a specific configuration file to automate PR drafting and target branch selection?▼

Yes, a JSON configuration file is required to automate PR drafting and target branch selection. This file defines parameters including the default target branch, issue pattern, PR language, commit language, and default drafting behavior.

What is the best way to maintain a repeatable git workflow for pull requests across a team?▼

The best way to maintain a repeatable git workflow is to standardize PR creation through automation, grouping commits by feature and applying consistent multilingual descriptions. This enforces uniform branching and issue linking across the team.

Why should I configure draft by default when automating pull requests?▼

Configuring draft by default prevents incomplete automated PRs from being merged prematurely. It creates a review buffer where team members can verify generated multilingual descriptions and issue links before publishing the final pull request.

Related Skills

Explore More Software Engineering Skills→
leejaedusleejaedus

configure-telegram

Configure Telegram notifications for Claude Code sessions via JSON configuration.

Community
Advanced
novel-jpnovel-jp

learn-gw-pr

Create a GitHub pull request and link it to a ProjSight task.

Official
Intermediate
hairihouhairihou

git-conventions

Enforce Conventional Commits syntax for Git commit messages and branch naming.

Community
Basic
paultyngpaultyng
9

ship-it

Automate Git pre-commit checks, changelog generation, and GitHub pull request updates.

Community
Advanced