ce-commit-push-pr

Commit changes, push branches, and generate GitHub PR descriptions.

10|Updated Dec 13, 2016
One-click install
npx skills add https://github.com/vitallium/dotfiles --skill ce-commit-push-pr-vitallium
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-commit-push-pr
Source: https://github.com/vitallium/dotfiles/tree/main/dot_agents/skills/ce-commit-push-pr
Command: npx skills add https://github.com/vitallium/dotfiles --skill ce-commit-push-pr-vitallium

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Committing changes and coordinating a PR is tedious and error-prone when handling different development modes and branch states. This skill automates the end-to-end Git workflow from commit to PR, including adaptive PR descriptions, branch resolution, and optional description rewriting to reflect observable changes.

Core Features & Use Cases

  • End-to-end Git workflow: detect base branch, create a feature branch when needed, commit grouped changes, push to origin, and open or update a GitHub PR with a value-first description.
  • Description-first formatting: when describing changes, generate PR bodies that emphasize what changed and why, aligned with observable outcomes.
  • Flexible modes: supports description-only, description-update, and full workflow (including commit/push) flows.
  • Evidence-aware PRs: integrates guidance for capturing or referencing evidence in the PR description and allows rewriting descriptions when requested.
  • Branch safety: uses a safe branch-creation flow that respects unpushed commits and remote state.

Quick Start

Create a feature branch from the default branch, commit changes, push, and open a PR with an adaptive, value-first description.

Frequently Asked Questions about ce-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 in one workflow?

You can automate git commit, push, and pull request creation by using a tool that detects the base branch, commits grouped changes, creates a feature branch, pushes to the remote, and opens a GitHub PR with an adaptive description.

How do I generate a value-first PR description from my git commit history?

Generating a value-first PR description involves analyzing your git commit history and observable changes to emphasize what changed and why, aligning the PR body text with observable outcomes rather than just listing commit messages.

Can I update an existing GitHub PR description without creating a new branch?

Yes, you can update an existing GitHub PR description without creating a new branch by using a description-update mode that rewrites the PR body to reflect the latest observable changes while keeping the current branch intact.

What is a safe branch creation flow when pushing unpushed commits to GitHub?

A safe branch creation flow respects unpushed commits and remote state by checking the default base branch before creating a feature branch, ensuring no local changes are lost during the git push and PR process.

Does the GitHub CLI support generating adaptive PR titles and bodies?

Yes, the GitHub CLI supports generating adaptive PR titles and bodies by integrating with workflow tools that compose conventional-commit guided text and evidence-aware descriptions directly into the pull request creation command.

What are the limitations of automating git workflow and PR generation?

Limitations of automating git workflow and PR generation include potential misalignment of conventional-commit guidance if commit messages are ambiguous, and dependency on the GitHub CLI for accurate title and body composition during the pull request creation process.