skills.rest
Room-C
Room-COFFICIAL
Explore all skills by this author →
GitHub

rc:commit-pr

Stage changes, commit with conventional messages, push, and create pull requests via GitHub CLI.

Updated Apr 10, 2026
Search Tags:#automation#git#workflow#github#pull-request#conventional-commits
One-click install
npx skills add https://github.com/Room-C/ai-dev-workflow --skill rc-commit-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rc:commit-pr
Source: https://github.com/Room-C/ai-dev-workflow/tree/main/skills/commit-pr
Command: npx skills add https://github.com/Room-C/ai-dev-workflow --skill rc-commit-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh.

What problem does it solve?

This skill automates the repetitive and error-prone process of staging changes, generating conventional commit messages, pushing to remote, and creating or updating Pull Requests.

Core Features & Use Cases

  • Automated Workflow: Handles the entire sequence from staging files to opening a ready-for-review PR in one command.
  • Safety Guardrails: Includes automatic secret detection to prevent accidental commits of sensitive files and verifies PR status to avoid duplicate work.
  • Use Case: When you finish a feature, simply run this skill to commit your changes with a standardized message and open a PR against the main branch without leaving your terminal.

Quick Start

Use the rc:commit-pr skill to commit all current changes and open a pull request targeting the main branch.

Frequently Asked Questions about rc:commit-pr

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

FAQPage Schema
How do I automate Git commit and pull request creation in one command?▼

Automating your Git commit and pull request workflow involves a single command that stages changes, generates conventional commit messages, pushes to the remote, and opens a PR via the GitHub CLI automatically.

What is a conventional commit workflow and how does it manage PRs?▼

A conventional commit workflow standardizes Git history by enforcing specific message formats during staging and pushing, which then automates pull request delivery against the main branch for consistent logs.

Do I need the GitHub CLI installed to automate pull requests from the terminal?▼

Yes, automating pull requests from the terminal requires the GitHub CLI (gh) installed. The workflow integrates directly with gh to verify PR status and manage the pull request lifecycle without duplicates.

How do I prevent accidentally committing secret files when pushing to GitHub?▼

To prevent committing secret files to GitHub, use an automated workflow with built-in safety guardrails that provide automatic secret detection to filter sensitive files before staging changes.

What is the best way to synchronize branches before opening a pull request?▼

The best way to synchronize branches before opening a pull request is using an automated workflow that verifies PR status, avoids duplicate work, and handles branch synchronization during the push process.

Why does my automated pull request workflow create duplicate PRs?▼

Automated pull request workflows create duplicates if they lack PR status verification. A properly configured workflow checks existing PR status before creation to prevent duplicate work and maintain branch synchronization.

Related Skills

Explore More Software Engineering Skills→
Tx1207Tx1207
5

project-creator

Create a new project from a template, initialize uv, and configure a local Git repository.

Community
Advanced
Jamie-CuiJamie-Cui
28

finishing-a-development-branch

Finalize feature branches with pre-integration checks and merge strategy guidance.

Community
Intermediate
cartridge-ggcartridge-gg
80

pre-commit-check

Run Husky pre-commit hooks for format, lint, and test checks.

Official
Intermediate
pwretmopwretmo

worktree-workflow

Automate git worktree setup, validation, commit, push, and PR creation via MCP.

Community
Advanced