pull-request

Turn an in-progress code change into a merge-ready GitHub pull request.

142|13|Updated Nov 8, 2025

Search Tags:#code review #pull requests #rust #github cli #review automation #ci checks #screenshot verification

Ready to run

npx skills add https://github.com/noh-rs/nohrs --skill pull-request-noh-rs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/noh-rs/nohrs/tree/main/.claude/skills/pull-request
Command: npx skills add https://github.com/noh-rs/nohrs --skill pull-request-noh-rs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, python3, and includes scripts (resource) components.

What problem does it solve?

It turns an in-progress change into a merge-ready GitHub pull request without leaving review gaps behind.

Core Features & Use Cases

Local quality gate with formatting, linting, build, and test checks before anything is pushed.
Pull request creation or update with repo-specific title and body hygiene rules.
Review-loop automation for resolving CodeRabbit and cubic feedback, plus optional UI verification with screenshots for visible changes.
Example: use it when you need to ship a Rust change, attach verification evidence, and keep iterating until the PR is green.

Quick Start

Ask the skill to take the current working tree to a merge-ready pull request and keep fixing review feedback until all checks pass.

Frequently Asked Questions about pull-request

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

FAQPage Schema

How do I turn my Rust code changes into a merge-ready pull request?▼

To turn Rust code changes into a merge-ready pull request, run local quality gates for formatting, linting, building, and testing. The process then pushes passing changes and applies repo-specific title and body hygiene rules to the PR.

How does pull request review automation handle CodeRabbit and cubic feedback?▼

Pull request review automation iterates on CodeRabbit and cubic feedback by tracking unresolved review threads. It automatically addresses requested changes and continues fixing issues until all CI checks pass.

Do I need GitHub CLI authentication to automate pull request creation?▼

Yes, GitHub CLI authentication is required to automate pull request creation and updates. You also need local git and python3 installed to execute the quality gate scripts and review-loop automation.

Can I attach screenshot verification to UI changes in a GitHub pull request?▼

Yes, you can attach screenshot verification to UI changes in a GitHub pull request. The workflow captures visual evidence for visible changes and attaches it to the PR to verify UI behavior during review.

What's the best way to ensure CI checks pass before pushing a Rust pull request?▼

The best way to ensure CI checks pass before pushing a Rust pull request is running local quality gates. This step executes formatting, linting, build, and test checks locally so only verified changes are pushed to GitHub.

Why does my pull request automation fail when local Rust quality gates are not met?▼

Pull request automation fails when local Rust quality gates are not met because it prevents broken changes from being pushed. The workflow requires formatting, linting, build, and test checks to pass before creating the PR.