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.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "git" with this command: npx skills add cfircoo/claude-code-toolkit/cfircoo-claude-code-toolkit-git

<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 <noreply@anthropic.com>

Use HEREDOC for multi-line messages:

git commit -m "$(cat <<'EOF'
Message here

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

Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"

</commit_format>

<pr_format> PR body structure:

## 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>

WorkflowPurpose
commit.mdStage changes and create commit with proper message
push.mdPush commits to remote, create branch if needed
pr.mdCreate pull request with gh CLI
</workflows_index>

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

sqlalchemy-postgres

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

generate-prd

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

pytest-best-practices

No summary provided by upstream source.

Repository SourceNeeds Review