commit-and-pr

Stage files, draft commit messages, and create pull requests with user confirmation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/rensjaspers/agents --skill commit-and-pr-rensjaspers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-and-pr
Source: https://github.com/rensjaspers/agents/tree/main/skills/commit-and-pr
Command: npx skills add https://github.com/rensjaspers/agents --skill commit-and-pr-rensjaspers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of committing code changes and creating pull requests, ensuring a smooth and user-confirmed workflow for version control.

Core Features & Use Cases

  • Guided Git Operations: Assists users through staging, committing, and creating pull requests.
  • User Confirmation: Requires explicit user approval before executing any git commands or creating PRs.
  • Safety First: Implements safety rules to prevent accidental data loss or security breaches.
  • Use Case: After completing a feature, use this skill to easily commit your changes and open a pull request for review, with clear visibility into the commit message and PR details before they are finalized.

Quick Start

Use the commit-and-pr skill to commit my changes and create a pull request.

Frequently Asked Questions about commit-and-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 safely?

Automating git commit and pull request creation safely requires explicit user confirmation before executing commands. This workflow stages relevant files, drafts conventional commit messages, and creates pull requests with summaries while ensuring user approval at every step.

What is the standard workflow for creating a GitHub pull request after staging changes?

The standard workflow for creating a GitHub pull request involves staging modified files, drafting a conventional commit message, and executing `gh pr create` with a summary and test plan. This guided process requires explicit user approval before finalizing the pull request.

Do I need to manually write commit messages when using a guided git operations workflow?

You do not need to manually write commit messages when using a guided git operations workflow. The process drafts commit messages following established conventions automatically, but it requires your explicit approval before executing the final git commit command.

Can I review git commit details before the changes are pushed to version control?

You can review git commit details before changes are pushed to version control. The workflow provides clear visibility into the staged files, drafted commit messages, and pull request details, requiring your explicit confirmation before executing any git or gh commands.

How to prevent accidental data loss when executing git commands to open a pull request?

Preventing accidental data loss when executing git commands to open a pull request requires implementing strict safety rules and user confirmation checks. The workflow pauses for explicit approval before staging files, committing changes, or creating the pull request.