skills.rest
jellyrock
jellyrockOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pr

Create or update JellyRock Roku pull requests with GitHub CLI.

37|2|Updated Jun 28, 2025
Search Tags:#code review#pull request#github#pr automation#tech-debt#jellyrock#journal hygiene
One-click install
npx skills add https://github.com/jellyrock/jellyrock --skill pr-jellyrock
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/jellyrock/jellyrock/tree/main/.claude/skills/pr
Command: npx skills add https://github.com/jellyrock/jellyrock --skill pr-jellyrock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious, error-prone manual work of creating and updating pull requests for the JellyRock Roku client, including the risk of duplicate PRs, missing related issues and architecture docs, and forgetting to capture tech-debt or decision entries as part of the shipping workflow.

Core Features & Use Cases

  • Create or update PRs automatically: Detects if an open PR already exists for your branch and routes to update mode (diff, confirm, edit) instead of creating a duplicate, while aborting cleanly on merged or closed PRs.
  • Automated journal hygiene: Runs four built-in judgment passes to surface tech-debt entries, decision records, and follow-ups before the PR is opened, so documentation stays in sync with code changes without extra manual work.
  • Smart context gathering: Automatically fills the PR template's Issues and Docs sections with real signal from your branch (related issues, touched architecture docs) instead of requiring you to hunt for links manually. Use case: For example, if you push a branch that fixes a playback bug and touches the OSD module, the Skill will automatically link the related GitHub issue, flag any tech-debt items introduced by the change, and populate the Docs section with the relevant architecture files you modified.

Quick Start

Use the pr skill when you are ready to ship a completed feature or bug fix branch for the JellyRock repo to generate a properly formatted pull request with all required context and journal entries.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate pull request creation to avoid missing journal hygiene steps?▼

Automating pull request creation handles template filling, issue linking, and pre-PR judgment passes for tech-debt entries. It eliminates manual PR formatting and ensures documentation stays in sync with code changes by running automated checks before opening the PR.

How does PR automation handle existing open pull requests for the same branch?▼

PR automation detects if an open pull request already exists for your branch and routes to update mode instead of creating a duplicate. It cleanly aborts if the existing PR is already merged or closed, preventing redundant pull requests.

Do I need the GitHub CLI to automate pull request creation and updates?▼

Yes, you need the GitHub CLI (gh) authenticated with repository access to automate pull request creation. You also need a non-main, non-detached branch with a clean working tree and an upstream configuration to execute the workflow.

What is the best way to capture tech-debt and decision records before opening a pull request?▼

The best way to capture tech-debt and decision records is running built-in judgment passes before the pull request is opened. This automated pre-PR check surfaces decision records, follow-ups, and tech-debt entries so documentation stays aligned with code changes.

Can I automatically populate architecture docs and related issues in my PR template?▼

Yes, automated smart context gathering fills the PR template's Issues and Docs sections with real signal from your branch. It automatically links related GitHub issues and populates the Docs section with relevant architecture files you modified.

What happens if I try to create a pull request on a detached HEAD or unclean working tree?▼

The PR creation process requires a non-detached branch with a clean working tree and upstream configured. If these conditions are not met, the automation will fail to execute properly, ensuring pull requests are only generated from valid branch states.

Related Skills

Explore More Software Engineering Skills→
haryelramalhoharyelramalho

create-pr-with-template

Create a GitHub pull request with a repository template and branch validation.

Community
Advanced
NVIDIANVIDIA
3.4k

release-cherry-pick

Cherry-pick labeled merged pull requests into release branches via GitHub CLI.

Official
Advanced
golemcloudgolemcloud
19

finalizing-pr

Build, lint, and format Rust code with Cargo and Clippy before pull request submission.

Official
Intermediate
softwaresaltsoftwaresalt
2

fix-ci

Automate CI pipeline failure fixes on GitHub pull requests.

Community
Advanced