oss-pr

Automate branch management, checks, and pull request creation in GitHub-style pipelines.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mitchlabeetch/Largarda --skill oss-pr-mitchlabeetch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oss-pr
Source: https://github.com/mitchlabeetch/Largarda/tree/main/.agents/skills/oss-pr
Command: npx skills add https://github.com/mitchlabeetch/Largarda --skill oss-pr-mitchlabeetch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the end-to-end OSS PR workflow by automating branch handling, quality checks, and PR creation for faster code reviews.

Core Features & Use Cases

  • Automates branch creation naming and switching based on changes to keep PRs organized.
  • Runs pre-commit checks, linting, and tests to ensure code quality before pushing.
  • Opens and summarizes pull requests, enabling quick stakeholder reviews.
  • Use case: after finishing a feature, OSS PR automates the sequence from branch setup to PR publication.

Quick Start

Commit your changes and run oss-pr to automatically push a feature branch, execute checks, and open a 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 a local git commit?

Automating pull request creation from a local git commit involves orchestrating branch management, running pre-commit checks, and opening the PR. This Skill streamlines that sequence by automatically handling branch naming, executing tests, and publishing the PR.

What is the best way to streamline an OSS PR workflow with automated branch management?

Streamlining an OSS PR workflow requires automating branch creation, switching, and quality checks. This Skill applies deterministic branch naming to keep PRs organized and enforces quality gates by running linting and tests before pushing.

Can I enforce CI checks and linting before opening a pull request automatically?

Yes, you can enforce CI checks and linting before opening a pull request automatically. This Skill runs pre-commit checks and tests to ensure code quality, then opens and summarizes the PR for stakeholder review only if those gates pass.

Does automating GitHub-style PR pipelines require access to the remote repository?

Automating GitHub-style PR pipelines requires a local git repository context and access to the target remote. You also need supporting scripts to perform deterministic branch naming, run tests, and open PRs successfully.

When should I not use an automated pull request workflow for code reviews?

You should not use an automated pull request workflow if your changes require manual branch naming, lack local git repository context, or need custom quality checks outside the pre-commit, linting, and test scripts this automation supports.