signal-pr

signal-pr is a skill for Claude Code from mattbaconz/signal. It costs 62 tokens per session (1,230 once invoked), scanned A, original, MIT.

A skill that stages changes, commits them, pushes the branch, and opens a pull request using the GitHub CLI. A pull request is a request for others to review and merge a set of changes.

In plain words
What is it for?
Creating pull requests from current work, generating a change summary and type, pushing new branches, and using draft or dry-run options when requested.
Why use it?
Preparing a pull request manually involves repeating the same Git and GitHub steps. This automates that workflow and builds the title and description from the changes.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the signal plugin — 8 skills shipped together

Good fit Creating pull requests from current work, generating a change summary and type, pushing new branches, and using draft or dry-run options when requested.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mattbaconz/signal/signal-pr
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add mattbaconz/signal --skill signal-pr
Clone the repo
git clone --depth 1 https://github.com/mattbaconz/signal

Made for: Claude Code.

Or install signal, the plugin that ships this one along with the rest of its 8 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for signal-pr

README.md
[![agentmods](https://agentmods.dev/badge/skills/mattbaconz/signal/signal-pr/github.svg)](https://agentmods.dev/skills/mattbaconz/signal/signal-pr)
Your own site
<a href="https://agentmods.dev/skills/mattbaconz/signal/signal-pr"><img src="https://agentmods.dev/badge/skills/mattbaconz/signal/signal-pr/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for signal-pr

Your own site · 80×15
<a href="https://agentmods.dev/skills/mattbaconz/signal/signal-pr"><img src="https://agentmods.dev/badge/skills/mattbaconz/signal/signal-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,230 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.01230
Opus 5 $0.00031 $0.00615
Sonnet 5 $0.00012 $0.00246
Haiku 4.5 $0.00006 $0.00123

Measured 12d ago against content hash 0c50a64edfcf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

signal-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/pr.ps1, scripts/pr.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

claude-signal/skills/signal-pr/SKILL.md · 170 lines

How it starts

The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.

⚡ signal-pr — Commit + Push + PR

One command. Stages, commits, pushes, opens a PR. Done.


Invocation Triggers

Activate when user says any of:

  • /signal-pr
  • "open a PR", "create pull request", "ship a PR", "make a PR"
  • "commit push and PR", "PR this"

Slash command behavior

If the user's message is only /signal-pr (optionally with flags like --dry, --draft, or --pr-draft), treat that as execute now.

  • Do not stop after acknowledging the skill.
  • Do not ask for confirmation unless the user explicitly requested review mode.
  • Immediately run the ordered steps below in the same turn.
  • Respect --dry, --draft, and --pr-draft exactly as defined in this file.

Behavior (Ordered Steps)

  1. Run signal-push logic — stages, commits, pushes. See signal-push/SKILL.md for complete push behavior.

  2. Generate PR title

    • Derived from commit message(s)
    • Single commit: use commit message as-is
    • Multiple commits: synthesize a title covering the change set
    • Max 72 chars, same rules as commit messages
  3. Generate PR body using this exact template:

    ## Changes
    - {change 1}
    - {change 2}
    
    ## Type
    {feat|fix|refactor|chore|docs|test|style|perf}
    
    Closes #{issue_number}
    
    • Changes: bullet list derived from diff, grouped by type. No fluff.
    • Issue number: extracted from branch name if present (e.g. feat/PROJ-123-thingCloses #123)
    • Omit Closes # line if no issue number detectable
  4. Open the PR

    gh pr create --title "{title}" --body "{body}"
    
  5. Report

    ✓ feat(auth): add JWT refresh token rotation [3 files, +47/-12]
    ✓ pushed → origin/feat/jwt-refresh
    ✓ PR opened → https://github.com/org/repo/pull/142
    

PR Body Template

## Changes
- {change 1}
- {change 2}

## Type
{feat|fix|refactor|...}

Closes #{issue_number if detectable from branch name}

Rules:

  • Changes are imperative phrases, max 80 chars each: "add JWT refresh token rotation"
  • Group by type if multiple types present (feat changes, then fix changes, etc.)
  • No prose, no explanation, no "this PR introduces"
  • No emoji

Read the full file on GitHub · 170 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 170 lines · 62 tokens per session scan A 0c50a64edfcf

Subscribe to this mod's changes

signal-pr is a skill published in the GitHub repository mattbaconz/signal (10 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 1,230 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

commit-staged

This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or explicitly invokes "commit-staged".

fcakyon/claude-codex-settings · 46 tokens

lov-checkpoint-list

A read-only history report built from Git records and project checkpoint logs. A checkpoint is a recorded project milestone or state, while Git is the version-control system that tracks changes and commits.

lovstudio/skills · 38 tokens

lov-git-commit-with-context

A Git commit helper that compares the current conversation's intended work with the repository's actual changes before creating a commit. Git is a system for tracking file changes, and a commit records a selected set of those changes.

lovstudio/skills · 47 tokens

chinese-commit-conventions

A Chinese-language convention for writing Git commit messages, based on Conventional Commits, a standard format that tools can use to classify changes and build changelogs.

Leodorareluctant259/superpowers-zh · 28 tokens

atomic-commits

Commit discipline for every repository — small atomic commits, Conventional Commits messages, only commit working states. Use whenever creating git commits, splitting work into commits, or writing commit messages, in any project.

AkshitIreddy/agent-skills · 45 tokens

git-workflow-and-versioning

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…

addyosmani/agent-skills · 89 tokens