oss-pr

Automate branch creation, code quality checks, and PR creation from local changes.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/gerald-ica/opencode-config-snapshot --skill oss-pr-gerald-ica
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oss-pr
Source: https://github.com/gerald-ica/opencode-config-snapshot/tree/main/opencode/skills/oss-pr
Command: npx skills add https://github.com/gerald-ica/opencode-config-snapshot --skill oss-pr-gerald-ica

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically streamlines the pull request lifecycle for open-source projects by handling branch creation, pre-commit checks, and PR creation from local changes.

Core Features & Use Cases

  • Auto-generates feature branches from changes and enforces conventional naming.
  • Runs format, lint, and type checks, then commits and pushes changes.
  • Creates a PR with a descriptive title and body for collaboration workflows.

Quick Start

Ask your AI to run the OSS PR workflow on the current repository to convert local changes into a ready-to-review PR.

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 from local changes?

Automating pull request creation from local changes involves running pre-commit checks like format, lint, and type checking, then auto-generating a descriptive title and body for the PR to streamline collaboration.

What is the best way to enforce conventional branch naming for feature branches?

Enforcing conventional branch naming for feature branches requires an automated workflow that validates branch names against deterministic naming conventions before committing and pushing local code changes.

Can I run format, lint, and TypeScript checks before opening an OSS PR automatically?

Running format, lint, and TypeScript checks before opening an OSS PR can be automated by executing code quality checks sequentially during the pull request workflow prior to commit generation.

Does the automated PR workflow support i18n checks and test execution?

The automated PR workflow supports i18n checks and test execution, running these validations when applicable to ensure code quality requirements are satisfied before PR creation.

How do I generate commit messages automatically during the PR workflow?

Generating commit messages automatically during the PR workflow requires a system that analyzes local changes and produces deterministic commit messages to satisfy repository collaboration requirements.

What is an end-to-end pull request workflow for open source contributions?

An end-to-end pull request workflow for open source contributions handles branch creation, executes pre-commit code quality checks, and automatically opens a PR with a descriptive title and body.