ce-commit-push-pr

Commit, push, and open GitHub pull requests with adaptive value-first descriptions.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Norfolk-Group/marcela-norfolk-ai --skill ce-commit-push-pr-norfolk-group
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-commit-push-pr
Source: https://github.com/Norfolk-Group/marcela-norfolk-ai/tree/main/skills/compound-engineering/skills/ce-commit-push-pr
Command: npx skills add https://github.com/Norfolk-Group/marcela-norfolk-ai --skill ce-commit-push-pr-norfolk-group

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing meaningful commit messages and PR descriptions is repetitive and often produces cookie-cutter templates that reviewers ignore. This Skill takes you from uncommitted working changes to an open pull request in one step, generating descriptions whose depth scales with the complexity of the change. ## Core Features & Use Cases - Full workflow automation: Detects branch state, creates feature branches from a fresh remote base, groups changes into logical commits, pushes, and opens the PR via the GitHub CLI. - Adaptive PR descriptions: Resolves the full commit range and diff, classifies feature vs. fix-up commits, and composes titles and bodies that lead with value, including Mermaid diagrams or tables when structure warrants them. - Description-only and update modes: Generate a PR description without touching git state, or rewrite the description of an existing open PR with user confirmation. - Use Case: You finished a bugfix across three files on a feature branch. Say "ship this" and the Skill commits the changes with conventional-commit messages, pushes, and opens a PR whose description explains what was broken and what now works. ## Quick Start Ask the assistant to commit my current changes, push the branch, and open a pull request with a well-written 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 commit, push, and open a GitHub PR in one step?

Invoke the skill with a phrase like "ship this" or "commit and PR". It inspects git status and diff, groups changes into logical commits following repo conventions, pushes with git push -u origin HEAD, and opens the PR using gh pr create with a composed title and body.

How do I update an existing pull request description?

Ask to update, refresh, or rewrite the PR description. The skill finds the open PR on the current branch via gh pr view, resolves the full commit range, composes a new title and body, shows a preview of the summary, and applies it with gh pr edit only after you confirm.

Can I generate a PR description without committing or pushing?

Yes. Phrases like "write a PR description" or "describe this PR" trigger description-only mode, which skips all git mutations. You can also paste a PR URL or number to describe a specific pull request's commit range.

What happens if I run this on the default branch with uncommitted changes?

The skill fetches the fresh remote base, checks for unpushed local commits, and asks whether to carry them onto a new feature branch or leave them behind. It never pushes directly to the default branch and handles stash-retry-pop if checkout collides with local edits.

Does the PR description include screenshots or demo evidence?

Only when the diff changes observable behavior such as UI, CLI output, or API responses. The skill asks before capturing evidence via the ce-demo-reel skill, preserves existing Demo or Screenshots sections, and skips evidence entirely for docs-only or internal refactor changes.

What are the limitations of the automated PR workflow?

It requires the GitHub CLI (gh) and a GitHub remote. Fork-based PRs without a matching remote fall back to API-only diff resolution, and fetch failures trigger a local-HEAD branch fallback with a note that base freshness was not verified.