Git Commit Push Pr

Organization

devoxx

git-commit-push-pr

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.

Overview

Publisher	devoxx
Repository	`DevoxxGenieIDEAPlugin`
Skill name	`git-commit-push-pr`
Stars	684
Forks	103
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by devoxx on GitHub. Read the source before you install it.

Installation

Install the Git Commit Push Pr AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/devoxx/DevoxxGenieIDEAPlugin/tree/master/.claude/skills/git-commit-push-pr
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/devoxx/DevoxxGenieIDEAPlugin/tree/master/.claude/skills/git-commit-push-pr

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/devoxx/DevoxxGenieIDEAPlugin.git /tmp/DevoxxGenieIDEAPlugin
mkdir -p .claude/skills
cp -r /tmp/DevoxxGenieIDEAPlugin/.claude/skills/git-commit-push-pr .claude/skills/git-commit-push-pr

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Git Commit Push Pr in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Git Commit Push Pr on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Git Commit Push Pr is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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).

Frequently asked questions

What does the Git Commit Push Pr AI skill do?

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.

Why use Git Commit Push Pr on TypingMind?

Because you install it once and use it with any model. Git Commit Push Pr is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Git Commit Push Pr in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/devoxx/DevoxxGenieIDEAPlugin/tree/master/.claude/skills/git-commit-push-pr. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Git Commit Push Pr?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Git Commit Push Pr?

As many as you like. As long as a model supports skills, you can use Git Commit Push Pr with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Git Commit Push Pr AI skill free?

Yes. It is published on GitHub by devoxx under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Deslop

openclaw

OrganizationPopular

Diff-scoped AI-slop cleanup pass: strip comment slop, defensive-check slop, type-laundering, and style drift from the current branch diff before autoreview.

Discord Clawd

Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.

Discrawl

Discord archive: search, sync freshness, DMs, summaries, TUI, repo/release work.

Gitcrawl

GitHub archive: issue/PR search, sync freshness, duplicate clusters, current GitHub handoff, and Gitcrawl repo work.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Git Commit, Push & PR

Context

Your task

Step 1 — Analyze changes and plan commits

Step 2 — Commit

Step 3 — Push

Step 4 — Pull Request

Step 5 — Report

Rules

Frequently asked questions

Related AI Skills

Set up your own AI workspace now