Skip to content
Skills Library
Programming · Review & audit

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.

Licence
Apache-2.0
Last repository change
26.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

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

  1. Commit Message Format
  2. Conflicts and Rebasing
  3. Prefer Modern Git Commands
Original SKILL.md headings · 32 lines, 203 words
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

RepositoryScoreLicence
This page · motlin/claude-code-plugins90Apache-2.0
event4u-app/agent-config100MIT
lee-w/maigo100MIT
hakula139/plugins100MIT
ericrisco/rsc-harness100MIT
Sanit-mann/The-Insectoids100MIT
eliyce/paqad-ai100MIT
langfuse/langfuse100MIT
Muvon/octomind-tap100Apache-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

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.