oss-pr

Name: oss-pr
Availability: InStock
Author: gaogg521

Automate branch creation, linting, testing, and pull request generation for Git projects.

33|6|Updated Apr 8, 2026

Search Tags:#automation #git #branching #ci-cd #code-review #pull-request #oss-pr

Ready to run

npx skills add https://github.com/gaogg521/1ONE-ClaudeCode --skill oss-pr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: oss-pr
Source: https://github.com/gaogg521/1ONE-ClaudeCode/tree/main/.claude/skills/oss-pr
Command: npx skills add https://github.com/gaogg521/1ONE-ClaudeCode --skill oss-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OSS PR workflow automates the end-to-end pull request process, reducing manual toil and ensuring consistent branch management, quality checks, and PR creation.

Core Features & Use Cases

Smart branch generation and naming based on changed files; auto-create and switch branches when on main, using a {username}/{type}/{slug} pattern.
Quality checks and tests before PR; run lint, type checks, tests, and optional i18n checks to guarantee code quality.
PR orchestration: commit, push, and create a PR with standardized messaging and formatting to accelerate code reviews.

Quick Start

Invoke the oss-pr workflow to automatically create a feature branch, run lint, execute tests, and open a pull request.

Frequently Asked Questions about oss-pr

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

FAQPage Schema

How do I automate pull request creation and branch management for Git?▼

Automating pull request creation involves using a single command workflow to handle branch generation, linting, testing, and PR orchestration. The process auto-creates a branch using a {username}/{type}/{slug} pattern when on main, ensuring consistent branch management.

What is the best way to run lint and type checks before opening a pull request?▼

Running lint and type checks before a pull request is best handled by an automated PR workflow that executes quality checks deterministically. This guarantees code quality by validating lint, types, and tests before committing and pushing changes.

How does smart branch naming work when automating CI-CD workflows?▼

Smart branch naming in automated CI-CD workflows generates branch names based on changed files. When operating on the main branch, the system auto-creates and switches to a new branch using a standardized {username}/{type}/{slug} naming pattern.

Can I use automated PR orchestration for code review across multiple environments?▼

Automated PR orchestration supports code review across multiple environments by applying deterministic branch naming, quality checks, and tests. It commits, pushes, and creates PRs with standardized messaging to accelerate reviews in Git-based projects.

Do I need optional i18n checks to automate my pull request workflow?▼

Optional i18n checks are not strictly required to automate your pull request workflow, but they can be included in the quality checks phase. The core workflow relies on lint, type checks, and tests to guarantee code quality before PR generation.