signal-pr

Stage, commit, push changes, and open a GitHub pull request via gh CLI.

10|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/mattbaconz/signal --skill signal-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signal-pr
Source: https://github.com/mattbaconz/signal/tree/main/gemini-signal/skills/signal-pr
Command: npx skills add https://github.com/mattbaconz/signal --skill signal-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates staging, committing, pushing changes, and opening a GitHub pull request.

Core Features & Use Cases

  • One-command workflow to stage, commit, push, and open a PR.
  • Automatically generates PR title and body from diffs and commits.
  • Supports dry-run, draft PRs, and pr-draft modes for safe, review-ready changes.
  • Use case: When completing a feature development, you run /signal-pr to quickly push and open PR with a ready-to-review summary.

Quick Start

Run /signal-pr to stage changes, push to origin, and automatically open a pull request.

Frequently Asked Questions about signal-pr

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

FAQPage Schema
How do I automate staging, committing, and opening a GitHub pull request in one command?

You can automate staging, committing, and opening a GitHub pull request by running a single command. It stages your changes, pushes them to your origin, and uses the gh CLI to generate the PR title and body from your diffs automatically.

Can I automatically generate a PR title and body from my git diff?

Yes, PR titles and bodies can be automatically generated from your git diff. The workflow parses your commits and diffs to produce consistent, ready-to-review pull request summaries without manual entry.

Does this automated pull request workflow support dry-run and draft PR modes?

This pull request workflow supports dry-run, draft, and pr-draft modes. These options allow you to safely preview changes or open incomplete pull requests for early review without affecting the main branch.

Do I need the gh CLI to automate pushing changes and creating pull requests?

Yes, you need the gh CLI installed to automate pushing changes and creating pull requests. The workflow relies on the gh CLI to interact with GitHub and open the ready-to-review PRs.

What is the best way to handle multi-commit changes when opening a pull request?

The best way to handle multi-commit changes when opening a pull request is using an automated workflow. It consolidates your commits, pushes the changes, and generates a comprehensive PR body from the combined diffs.

When should I not use an automated command to push and open a pull request?

You should not use an automated command to push and open a pull request when you need custom PR descriptions that cannot be generated from diffs, or when your changes require complex staging strategies outside of standard software development workflows.