Format code, review changes, commit, and push to remote
Scanned 9/2/2026
Install to Claude Code
npx -y skills add MarcusJellinghaus/mcp-workspace --skill commit_push --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Commit Push?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/marcusjellinghaus-commit-push)More formats (shields.io, HTML) on the badges page.
---
description: Format code, review changes, commit, and push to remote
disable-model-invocation: true
allowed-tools:
- mcp__mcp-workspace__git
- "Bash(git add *)"
- "Bash(git commit *)"
- "Bash(git push *)"
- mcp__mcp-tools-py__run_format_code
- mcp__mcp-workspace__read_file
- mcp__mcp-workspace__list_directory
- mcp__mcp-workspace__search_files
---
# Commit and Push Changes
Follow this process to commit and push your changes:
## 1. Format Code
Use `mcp__mcp-tools-py__run_format_code` to format all code (black + isort).
## 2. Review Changes
Use `mcp__mcp-workspace__git` with command `"status"` to check working directory state.
Use `mcp__mcp-workspace__git` with command `"diff"` to review the changes.
## 3. Stage Changes
Stage all relevant changes (exclude any files that shouldn't be committed).
## 4. Commit
Create a commit with a clear, conventional commit message:
- Use format: `type(scope): description`
- Types: feat, fix, docs, style, refactor, test, chore
- Keep summary under 50 characters
- **No Claude Code footer or attribution in commit message**
## 5. Push
```bash
git push
```
If the branch doesn't exist on remote yet:
```bash
git push -u origin HEAD
```
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.