跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

git-workflow

Commit message format and git workflow rules. ALWAYS use this skill for every git commit — no exceptions — and whenever rewording an existing commit message.

motlin · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add motlin/claude-code-plugins --skill git-workflow

技能说明


name: git-workflow description: Commit message format and git workflow rules. ALWAYS use this skill for every git commit — no exceptions — and whenever rewording an existing commit message.

Git Workflow

Commit with the git:commit skill.

Commit Message Format

Every commit message is a single line: no body, no bullet list, no extra paragraphs. It:

  • Starts with a present-tense verb (Add, Fix, Replace, Remove, Update, …)
  • Is 60-120 characters
  • Ends with a period
  • Avoids praise adjectives (comprehensive, robust, essential, best practices)

A task description or prompt is intent, not the message. Distill a long or multi-line prompt to one line; never copy it verbatim. This applies to new commits and to rewording existing ones with git history reword.

Conflicts and Rebasing

Resolve conflicts with the git:conflicts skill.

Rebase the current branch on upstream with the git:git-rebase skill.

Prefer Modern Git Commands

  • git switch instead of git checkout for switching branches
  • git switch -c instead of git checkout -b for creating branches
  • git restore instead of git checkout -- for restoring files
  • git restore --staged instead of git reset HEAD for unstaging files
  • git replay --onto instead of git rebase --onto for non-interactive onto rebases
  • git history reword instead of interactive rebase or amending for editing commit messages
  • git history split instead of interactive rebase for splitting commits