commit-push-pr

Automate git commits, feature-branch pushes, and gh pull-request creation with conventional commit enforcement and PR template auto-detection.

Updated Oct 29, 2013
One-click install
npx skills add https://github.com/whywaita/dotfiles --skill commit-push-pr-whywaita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-push-pr
Source: https://github.com/whywaita/dotfiles/tree/main/dot_codex/skills/commit-push-pr
Command: npx skills add https://github.com/whywaita/dotfiles --skill commit-push-pr-whywaita

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create git commits, push a feature branch, and open a Pull Request using gh, ensuring conventional commits and PR templates are respected.

Core Features & Use Cases

  • Conventional-commit formatting and automatic PR template alignment.
  • Branch management with automatic switching if needed and PR URL output.
  • Signed-commit attempts with fallback and clear error handling.

Quick Start

Ask the skill to commit changes, push a branch, and open a PR using gh.

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 with conventional commits?

Automating git commit, push, and pull request creation is achieved by enforcing conventional commit formats, pushing changes to a feature branch, and using gh to open a PR with an auto-detected template. It outputs the final PR URL upon completion.

Can I open a GitHub pull request with a PR template using gh automatically?

Yes, opening a GitHub pull request with a PR template using gh automatically is supported. The process auto-detects existing PR templates in your repository and aligns the pull request creation accordingly via the gh CLI tool.

What is the best way to enforce conventional commits when pushing a feature branch?

Enforcing conventional commits when pushing a feature branch is handled by formatting commit messages automatically before pushing. The process ensures your git history adheres to conventional commit standards and manages branch switching if required.

Does this automation handle signed commits and fallback if signing fails?

Yes, this automation handles signed commits by attempting to create them during the git commit phase. If signing fails, it utilizes a fallback mechanism and provides clear error handling to ensure the commit, push, and PR workflow continues smoothly.

How do I manage git branch switching and PR creation for solo projects?

Managing git branch switching and PR creation for solo projects is simplified through automatic branch detection and switching. It pushes your commits to the correct feature branch and generates the PR using gh, returning the direct PR URL.

Why does my conventional commit automation fail to open a PR via gh?

Conventional commit automation may fail to open a PR via gh due to missing dependencies or branch conflicts. The tool provides clear error handling during commit signing fallback and branch management to help diagnose push or PR creation failures.