git
Git operations for committing, pushing, and opening PRs using gh CLI. Use when performing version control tasks. This skill should be used when the user asks to "commit", "push", "create a PR", "ship code", "git status", or mentions git workflow, version control, or pull requests.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install cfircoo-claude-code-toolkit-git
Repository
Skill path: skills/git
Git operations for committing, pushing, and opening PRs using gh CLI. Use when performing version control tasks. This skill should be used when the user asks to "commit", "push", "create a PR", "ship code", "git status", or mentions git workflow, version control, or pull requests.
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: cfircoo.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install git into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/cfircoo/claude-code-toolkit before adding git to shared team environments
- Use git for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- name: git description: Git operations for committing, pushing, and opening PRs using gh CLI. Use when performing version control tasks. This skill should be used when the user asks to "commit", "push", "create a PR", "ship code", "git status", or mentions git workflow, version control, or pull requests. allowed-tools: Read, Bash, Glob, Grep argument-hint: [action or git operation] model: sonnet context: fork --- <essential_principles> <git_safety> **Never run destructive commands without explicit user request:** - No `git push --force` to main/master - No `git reset --hard` - No `--no-verify` flag (skip hooks) - No `git commit --amend` on pushed commits **Never push directly to main/master:** - If current branch is `main` or `master`, create a new branch before committing/pushing - Use a descriptive branch name based on the changes (e.g., `fix/login-bug`, `feat/add-filter`) - Only push to feature/fix branches, never directly to the default branch **Always verify before acting:** - Check `git status` before staging - Check `git log` for commit style - Check remote tracking before push </git_safety> <commit_format> End all commit messages with: ``` 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]> ``` Use HEREDOC for multi-line messages: ```bash git commit -m "$(cat <<'EOF' Message here 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]> EOF )" ``` </commit_format> <pr_format> PR body structure: ```markdown ## Summary <1-3 bullet points> ## Test plan - [ ] Test item 1 - [ ] Test item 2 🤖 Generated with [Claude Code](https://claude.com/claude-code) ``` </pr_format> </essential_principles> <intake> What would you like to do? 1. **Commit** - Stage and commit changes 2. **Push** - Push commits to remote 3. **PR** - Open a pull request 4. **Ship** - Full workflow: commit + push + PR **Wait for response before proceeding.** </intake> <routing> | Response | Workflow | |----------|----------| | 1, "commit", "stage" | `workflows/commit.md` | | 2, "push", "upload" | `workflows/push.md` | | 3, "pr", "pull request", "open pr" | `workflows/pr.md` | | 4, "ship", "full", "all" | Run commit → push → pr sequentially | **After reading the workflow, follow it exactly.** </routing> <workflows_index> | Workflow | Purpose | |----------|---------| | commit.md | Stage changes and create commit with proper message | | push.md | Push commits to remote, create branch if needed | | pr.md | Create pull request with gh CLI | </workflows_index>