Skip to content
Skills Library
Programming · Automation

commit-push-pr

/commit-push-pr

Analyze changes, create categorized conventional commits, push, and open a PR. Use when user asks to open a PR, invokes `/commit-push-pr`, or requests a full commit -> push -> PR flow with CI monitoring.

Repository
ui-harness ↗
Licence
MIT
Last repository change
24.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Analyze changes, create categorized conventional commits, push, and open a PR. Use when user asks to open a PR, invokes `/commit-push-pr`, or requests a full commit -> push -> PR flow with CI monitoring.

Original author description

Analyze changes, create categorized conventional commits, push, and open a PR. Use when user asks to open a PR, invokes `/commit-push-pr`, or requests a full commit -> push -> PR flow with CI monitoring.

How it works

  1. Step 0: Gather context
  2. Prerequisites
  3. Your task
Original SKILL.md headings · 95 lines, 597 words
SKILL.md preview
---
name: commit-push-pr
description: Analyze changes, create categorized conventional commits, push, and open a PR. Use when user asks to open a PR, invokes `/commit-push-pr`, or requests a full commit -> push -> PR flow with CI monitoring.
---

# Commit, push, and open PR

See [REFERENCE.md](REFERENCE.md) for commit-type table, auto-label map, PR body template.

## Step 0: Gather context

Run these Bash commands before proceed:

- `git status -sb` -- working-tree state
- `git diff HEAD` -- staged + unstaged changes
- `git branch --show-current` -- current branch
- `gh repo view --json defaultBranchRef -q '.defaultBranchRef.name'` -- default branch
- `git log --oneline -5` -- recent commits for style ref
- `gh pr list --head $(git branch --show-current) --json number,url,title --jq '.[0] // empty'` -- existing PR on branch

## Prerequisites

1. Verify `gh --version` -- if missing, stop, ask user install
2. Verify `gh auth status` -- if not authed, ask user run `gh auth login` and stop
3. Verify inside git repo

## Your task

Execute full commit-push-PR flow below in single response.

### Phase 0: Pre-flight -- verify review skill ran

Check REFERENCE.md for review skill list. If NONE ran this session, warn and block unless user confirms skip.

### Phase 1: Scope confirmation

1. Inspect status and diff above
2. PR exists on branch (from context) -> inform user, new commits update existing PR. Skip to Phase 3.
3. Worktree has unrelated changes -> **ask user** which files belong. Never default `git add -A`
4. Present file list grouped by category for confirmation before proceed

### Phase 2: Branch strategy

1. On default branch -> create new branch `type/description` (e.g. `feat/add-commit-push-command`) and switch
2. Else stay on current branch

### Phase 3: Categorized commits

Group changed files by conventional commit type (see REFERENCE.md type table).

**For each category with files:**

1. Stage only relevant files with explicit paths: `git add <file1> <file2> ...` -- never `git add -A` or `git add .`
2. Commit: `type(scope): terse description`
   - Infer scope from directory/module
   - Lowercase first letter, 5-72 chars, no trailing period
   - Include `Co-Authored-By` trailer
3. Next category

Record commit types created -- used for auto-labeling Phase 5.

### Phase 4: Push

1. Show what push: `git log --oneline origin/<branch>..HEAD 2>/dev/null || git log --oneline -5`
2. Push with tracking: `git push -u origin $(git branch --show-current)`
3. Never force push -- `--force-with-lease` OK when needed (after rebase)

### Phase 5: Open pull request

**PR exists** (from context) -> skip to Phase 6, push updated it already.

1. Determine base branch from context
2. Build `gh pr create` with `--base`, `--fill-verbose`, `--assignee @me`
3. Auto-label from commit types (see REFERENCE.md auto-label map)
4. Override auto-filled body with structured template (see REFERENCE.md PR body template)
5. Frontend change detected (REFERENCE.md rule) -> include Screenshots table summarizing visual changes. One row per affected view (before/after/notes). Omit section if no frontend diff
6. Print PR URL

### Phase 6: Watch CI (MANDATORY)

1. **Always** stream CI checks: `gh pr checks <PR_NUMBER> --watch` via Monitor tool
2. Never use `sleep` + polling -- use `--watch` flag
3. Never skip -- CI failures caught here save time
4. Checks fail -> read logs, diagnose, fix, commit, push, re-watch
5. No CI configured -> note and proceed

### Phase 7: Verify and summarize

1. Run `git status` and `git diff` to confirm clean worktree
2. Anything uncommitted remains -> warn user
3. Summarize: branch name, commits, PR URL (or existing PR URL), CI status, remaining user actions

### Safety

- Never stage unrelated changes silently
- Never push without confirming scope when worktree mixed
- Never force push -- `--force-with-lease` OK when needed (after rebase)
- No accessible git remote -> stop, explain blocker
- `gh pr create` fails -> show error, suggest `--recover` flag for retry
Files in this package (2)
  • REFERENCE.md 4 KB
  • SKILL.md 4 KB

Versions

RepositoryScoreLicence
This page · redpanda-data/ui-harness100MIT
gcwing/openbitfun100MIT
dyoshikawa/rulesync100MIT
gosuda/dalcom-skills100Apache-2.0
jeffh/claude-plugins100Apache-2.0
OutlineDriven/outline-driven-development100Apache-2.0
heyAyushh/stacc100MIT
heyAyushh/stacc100MIT
meleantonio/awesome-econ-ai-stuff100CC0-1.0

Database snapshot: 13.11.2026 · package version bf900d3b9860 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90commit-push
    Analyze changes, create categorized conventional commits, and push. Use when user asks to commit and push, invokes `/commit-push`, or requests conventional commits without a PR.
  • 91commit-push
    Commit with a Conventional Commits subject, then push. Use for /commit-push, "commit and push", "commit this and push". Must push. Never force-push.
  • 100branch-commit-pr
    Create a professionally named local git branch, commit the current changes in clean Conventional Commits (no Claude/AI signature), push it, and open a GitHub pull request. Use when the user asks to "make a branch and PR", "commit and open a PR", "ship these changes", or invokes /branch-commit-pr.
  • 82commit-push
    Commit with a Conventional Commits subject, then push. Use for /commit-push, "commit and push", "commit this and push". Must push. Never force-push.
  • 90ce-commit-push-pr
    Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
  • 95Commit
    Create a conventional-format commit, push, and open a GitHub PR that links the Jira ticket. GitHub is the source of record. Reuses buddy's SourceControl for commit formatting when available. USE WHEN sdlc commit, commit, create commit, open PR, push and PR, ship it, create pull…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.