git-commit-push-pr

Convert local worktree changes into a GitHub pull request with adaptive descriptions.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/sommio/RSSift --skill git-commit-push-pr-sommio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-push-pr
Source: https://github.com/sommio/RSSift/tree/main/.agents/skills/git-commit-push-pr
Command: npx skills add https://github.com/sommio/RSSift --skill git-commit-push-pr-sommio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps developers streamline the end-to-end process of turning local changes into a pull request by generating a value-driven PR description and coordinating branch management.

Core Features & Use Cases

  • Generate adaptive PR descriptions that scale with the complexity of the change to improve reviewer understanding.
  • Update existing PR descriptions when new commits are added or changes are requested.
  • Suggest descriptive feature branch names and manage branch creation across forks and remotes.
  • Detect base branches and appropriate remotes to ensure PRs target the correct repository.
  • Classify commits into feature vs fix-up to calibrate the narrative shown to reviewers.
  • Provide sizing guidance (small, medium, large) to tailor the description length.

Quick Start

Create a feature branch, commit your changes with meaningful messages, push to origin, and let the tool generate an adaptive PR description and open the pull request.

Frequently Asked Questions about git-commit-push-pr

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

FAQPage Schema
How do I generate a pull request description from local git commits?▼

You can generate a pull request description by analyzing local git commits to classify changes and sizing them to produce an adaptive, value-focused narrative for reviewers.

What's the best way to manage feature branches and push code to a remote repository for a PR?▼

Managing feature branches involves suggesting descriptive names, handling creation across forks and remotes, detecting the correct base branch, and pushing code to origin to open the pull request.

Can I update an existing PR description after adding new commits or addressing code review feedback?▼

Yes, existing PR descriptions can be updated when new commits are added or changes are requested, ensuring the reviewer narrative stays aligned with the latest code modifications.

How does commit classification affect pull request descriptions?▼

Commit classification separates features from fix-up commits to calibrate the narrative shown to reviewers, providing a cleaner and more accurate PR description.

Does this PR creation tool detect base branches across different forks and remotes?▼

Yes, the tool detects appropriate base branches and remotes to ensure that your pull requests target the correct repository, even when working across multiple forks.