git-workflow
/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.
- Author
- motlin ↗
- Repository
- claude-code-plugins ↗
- Licence
- Apache-2.0
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Commit message format and git workflow rules. ALWAYS use this skill for every git commit — no exceptions — and whenever rewording an existing commit message.
Original author 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.
How it works
- Commit Message Format
- Conflicts and Rebasing
- Prefer Modern Git Commands
SKILL.md preview
--- 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
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · motlin/claude-code-plugins | 90 | Apache-2.0 |
| event4u-app/agent-config | 100 | MIT |
| lee-w/maigo | 100 | MIT |
| hakula139/plugins | 100 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| Sanit-mann/The-Insectoids | 100 | MIT |
| eliyce/paqad-ai | 100 | MIT |
| langfuse/langfuse | 100 | MIT |
| Muvon/octomind-tap | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version a6816fa5934a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100commit
Write a commit message and create a git commit. Use when the user wants to commit changes, asks for a commit message, or says "commit this" or "make a commit". - 100commit
Use when writing a commit message, and MUST invoke before creating any git commit. Provides commit message format and safety rules. - 100git-commit
Use this skill when user asks to "commit changes", "create a commit", "stage and commit", or wants help with git commit workflow. - 100git-commit-format
Apply conventional commit formatting rules. Use when generating commit messages or creating commits. - 96commit
Use when writing a commit message, or before running `git commit`. - 100commit-message
Generate conventional commit messages - use when creating commits, writing commit messages, or asking for git commit help