skills.rest
LaiTszKin
LaiTszKinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

open-source-pr-workflow

Prepare review-ready pull requests with standardized branch naming and structured English PR bodies.

4|2|Updated Feb 25, 2026
Search Tags:#automation#workflow#code-review#pull-request#branch-naming#oss
One-click install
npx skills add https://github.com/LaiTszKin/apollo-toolkit --skill open-source-pr-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: open-source-pr-workflow
Source: https://github.com/LaiTszKin/apollo-toolkit/tree/main/open-source-pr-workflow
Command: npx skills add https://github.com/LaiTszKin/apollo-toolkit --skill open-source-pr-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open-source contributions often stall due to inconsistent PR quality. This Skill ensures a repeatable, high-quality PR workflow by guiding you from prepared changes to a ready-to-submit PR with standardized branch naming and English PR content.

Core Features & Use Cases

  • Enforces codex/{change_type}/{changes} branch naming for all PRs.
  • Drafts and opens PRs with required sections (motivation, engineering decisions with rationale, and test results) in English.
  • Default targets for forks to the upstream repository, unless the user explicitly requests the fork.
  • Provides a structured PR body to facilitate review and collaboration.

Quick Start

Draft a compliant PR by running the tool on prepared changes and verify the branch name codex/{change_type}/{changes} before opening.

Frequently Asked Questions about open-source-pr-workflow

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

FAQPage Schema
How do I prepare a review-ready pull request for an open-source repository?▼

To prepare a review-ready pull request, you must enforce standardized branch naming, draft the PR body in English with motivation and engineering decisions, and run edge-case discovery and code simplification checks before opening it.

What should be included in an OSS pull request body to pass code review?▼

An OSS pull request body should include structured sections for motivation, engineering decisions with rationale, and test results to facilitate review and collaboration for code-affecting changes.

How do I name branches for open-source contributions?▼

Branches for open-source contributions should follow the codex/{change_type}/{changes} naming convention to ensure consistency before drafting and opening a pull request.

Does a fork pull request target the upstream repository by default?▼

Yes, fork pull requests default to targeting the upstream repository unless you explicitly request to target your own fork during the workflow.

How to automate the open-source PR workflow for existing code changes?▼

To automate the open-source PR workflow, apply this process to existing changes: it enforces branch naming, runs code simplification and edge-case discovery for code changes, and drafts a structured PR body.

Can I use this PR workflow for documentation changes without running code checks?▼

Yes, this PR workflow applies to both code and documentation changes, but the discover-edge-cases and code-simplifier checks are only enforced for code-affecting changes.

Related Skills

Explore More Software Engineering Skills→
apocohqapocohq
4

cleanup-commits

Rebase a feature branch into logical commits for PR review.

Official
Intermediate
alistairsteadalistairstead

gh-pr-comments

List unresolved GitHub PR review comments and resolve threads by thread_id.

Community
Advanced
zapabobzapabob
2

qa-engineer

Automates QA engineering with Python-based test strategy design and code analysis.

Community
Advanced
TabooLibTabooLib
388

over-or

Push the current branch to a fork and create a PR to the main repository.

Official
Intermediate