skills.rest
Kikolator
KikolatorCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit-push-pr

Automate Git staging, commit, push, and pull-request creation.

Updated Mar 15, 2026
Search Tags:#automation#git#workflow#commit#branching#pull-request
One-click install
npx skills add https://github.com/Kikolator/claude-toolkit --skill commit-push-pr-kikolator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-push-pr
Source: https://github.com/Kikolator/claude-toolkit/tree/main/skills/commit-push-pr
Command: npx skills add https://github.com/Kikolator/claude-toolkit --skill commit-push-pr-kikolator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end Git workflow from staging to PR creation, reducing manual steps and human error.

Core Features & Use Cases

  • Automates commit, push, and PR creation for feature branches with conventional commits.
  • Enforces safe branching rules and upstream tracking to prevent commits on main or dev.
  • Generates PR bodies with summaries and context to aid code reviews in teams.

Quick Start

Commit your changes and let this skill manage the entire cycle.

Frequently Asked Questions about commit-push-pr

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

FAQPage Schema
How do I automate git commit, push, and pull request creation?▼

To automate git workflow, you can use a skill that handles the end-to-end cycle from staging to PR creation, enforcing consistent conventional commits and automated upstream pushes to reduce manual steps.

How does automated pull request creation work with conventional commits?▼

Automated pull request creation works by applying deterministic branching rules and conventional commit formatting, then generating a PR with a structured description and context summary to aid team code reviews.

Can I prevent commits directly on the main or dev branch?▼

Yes, enforcing safe branching rules prevents commits directly on main or dev branches by applying deterministic branching logic and managing upstream tracking for feature branches instead.

What is the best way to create feature branches with structured PR descriptions?▼

The best way to create feature branches with structured PR descriptions is to automate the end-to-end Git workflow, which enforces deterministic branching rules and generates PR bodies with summaries for code reviews.

Does automated git workflow handle upstream push tracking for new branches?▼

Yes, automated git workflow handles upstream push tracking by managing upstream pushes for new branches, ensuring feature branches are correctly tracked and pushed to the remote repository.

Why use conventional commit formatting in an automated git workflow?▼

Conventional commit formatting is used in an automated git workflow to ensure consistent commit messages across feature branches, reducing human error and generating structured PR descriptions for better code reviews.

Related Skills

Explore More Software Engineering Skills→
GLaDO8GLaDO8

smartcommit

Generates concise Git commit messages and commits staged or unstaged changes.

Community
Basic
mr-daedaliummr-daedalium
107

land-and-deploy

Merge PRs, trigger deployment, and verify canary health in CI/CD pipelines.

Community
Advanced
JohnRobert-OlanoJohnRobert-Olano

setup-pre-commit

Automate Husky pre-commit hook setup with lint-staged for formatting, type checks, and tests.

Community
Basic
andrew-t-jamesandrew-t-james

pr-create

Stage changes, create conventional commits, push with force-with-lease, and open a pull request via gh CLI.

Community
Intermediate