agentleFS
Sign inStart free
devoxxdevoxx/DevoxxGenieIDEAPlugin/.claude/skills/git-commit-push-pr/SKILL.md

git-commit-push-pr

Skill689 starsChanged 7 days agoMITView on GitHub

Commit all changes, push to remote, and open a pull request in one go. Use when the user says "commit push pr", "ship it", "open a pr", or invokes /git-commit-push-pr.

  • Reads credentials
  • Commits and pushes

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. htnabe/skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 10 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Before committing, analyze git status and git diff HEAD to identify logically distinct groups of changes.

    line 23
  2. Very specific:

    Create one commit per logical group identified above.

    line 33
  3. Distinctive:

    Write a clean, descriptive commit message for each commit using conventional commits style.

    line 34
  4. Distinctive:

    Use a HEREDOC to pass the commit message for correct formatting.

    line 37
  5. Distinctive:

    If the current branch is main or master, create a new feature branch first (use a descriptive name based on the changes).

    line 41
  6. Very specific:

    Create a PR using gh pr create targeting the main branch.

    line 46
  7. Distinctive:

    Keep the PR title short (under 70 characters), using conventional commit style.

    line 47
  8. Distinctive:

    Use a HEREDOC for the PR body with this format:

    line 48
  9. Distinctive:

    Do all steps in as few messages as possible.

    line 66
  10. Distinctive:

    Do not read or explore code beyond what git provides in the context above.

    line 67
  11. Very specific:

    Do not use interactive git flags (-i).

    line 68
  12. Distinctive:

    Never force-push or amend existing commits.

    line 69
  13. Distinctive:

    If a pre-commit hook fails, fix the issue and create a NEW commit (do not amend).

    line 70

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Git Commit, Push & PR

Context

  • Current git status: !git status
  • Current git diff (staged and unstaged changes): !git diff HEAD
  • Current branch: !git branch --show-current
  • Main branch: !git rev-parse --verify main 2>/dev/null && echo main || echo master
  • Recent commits: !git log --oneline -10

Your task

Review the changes in the repo and ship them as a pull request in one go.

Step 1 — Analyze changes and plan commits

Before committing, analyze git status and git diff HEAD to identify logically distinct groups of changes. Group by feature or concern — for example:

  • New files that form a self-contained module → one commit
  • Modifications to an existing file that depend on the new module → separate commit
  • Config or tooling changes → separate commit

Print a short commit plan (list of planned commits with the files in each) so the grouping is visible.

Step 2 — Commit

  • Create one commit per logical group identified above. Stage only the files for that group using explicit file names (never git add -A; never stage .env or credential files).
  • Write a clean, descriptive commit message for each commit using conventional commits style.
  • End every commit message with: Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
  • Use a HEREDOC to pass the commit message for correct formatting.

Step 3 — Push

  • If the current branch is main or master, create a new feature branch first (use a descriptive name based on the changes).
  • Push the branch to origin with -u to set upstream tracking.

Step 4 — Pull Request

  • Create a PR using gh pr create targeting the main branch.
  • Keep the PR title short (under 70 characters), using conventional commit style.
  • Use a HEREDOC for the PR body with this format:
## Summary
<1-3 bullet points describing the changes>

## Test plan
- [ ] <testing checklist items>

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Step 5 — Report

  • Print the PR URL so the user can see it.

Rules

  • Do all steps in as few messages as possible. Parallelize independent tool calls.
  • Do not read or explore code beyond what git provides in the context above.
  • Do not use interactive git flags (-i).
  • Never force-push or amend existing commits.
  • If a pre-commit hook fails, fix the issue and create a NEW commit (do not amend).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free