git-version-control

星标3

分支1

更新时间2026年4月13日 01:10

Always use this skill when using git!

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

cardoso-neto

cardoso-neto/personal-ai-infra

下载

Never use git add -A or git add . or checking to make sure only your changes are going to be included.
- Always prefer running git add <filename> <filename2>.
Commit message titles should be imperative, start capitalized, limited to 50 chars, and finish with no punctuation.
- Bulletpoint lists and other markdown syntaxes are encouraged inside commit message descriptions.
Do not create branches or commits unless explicitly told to do so.
When updating from the remote, always use git pull --rebase to avoid unnecessary merge commits.
Fix merge/rebase artifacts on the source branch, not the merge target.
- When a merge or rebase introduces a problem (duplicate imports, bad conflict resolution, etc.), trace it back to the feature branch that owns the change and fix it there.
- Amend the commit on the feature branch, force-push it, then redo the merge cleanly.
- Never patch these on master/main directly as it'd dirty up the commit history.

同仓库更多 Skills

同仓库

Explore and search previous Claude Code conversations stored in ~/.claude/projects/

Always use this skill when writing or editing python code!

Use this skill when working with software installed or run from local source checkouts that use git worktree hubs.

Always use this skill when writing or editing markdown files!

Always use this skill when writing or editing webscrapers!

Extracting text and tables, merging/splitting documents. Use when needing to convert PDFs while preserving structure.

name	git-version-control
description	Always use this skill when using git!

Never use git add -A or git add . or checking to make sure only your changes are going to be included.
- Always prefer running git add <filename> <filename2>.
Commit message titles should be imperative, start capitalized, limited to 50 chars, and finish with no punctuation.
- Bulletpoint lists and other markdown syntaxes are encouraged inside commit message descriptions.
Do not create branches or commits unless explicitly told to do so.
When updating from the remote, always use git pull --rebase to avoid unnecessary merge commits.
Fix merge/rebase artifacts on the source branch, not the merge target.
- When a merge or rebase introduces a problem (duplicate imports, bad conflict resolution, etc.), trace it back to the feature branch that owns the change and fix it there.
- Amend the commit on the feature branch, force-push it, then redo the merge cleanly.
- Never patch these on master/main directly as it'd dirty up the commit history.