Commit Rules Agent Skill

Shared commit message rules and technical constraints referenced by $stage-commit and $commit-staged. Not typically invoked directly.

241 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

398

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/tobihagemann/turbo --skill commit-rules

The instruction itself

3 sections, as written by the author

Commit Rules

Commit Message Rules

Match the style from git log -n 10 --oneline
Concise and descriptive
Imperative mood, present tense
Aim for ≤100 characters in the subject
No commit description—summarize everything in the message
Don't reference .turbo/ content (filenames, requirement IDs, shell references, headings) in commit messages. .turbo/ is gitignored, so these references would be opaque to anyone reading without local copies.

Technical Constraints

Use git commit -m "message" directly—do not use heredoc syntax (sandbox blocks temp file creation)
Never bypass commit signing (--no-gpg-sign, -c commit.gpgsign=false). If signing fails, use request_user_input to let the user resolve it—they may need to approve a key prompt.

Other skills for the same job

different authors, same section of the catalogue

Receiving Code Review

by ZhanlinCui

×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens

Requesting Code Review

by ZhanlinCui

×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Comprehensive GitHub code review with AI-powered swarm coordination

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

How to use it

Copy the folder

Take tobihagemann/turbo-commit-rules from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.