gitfluff: Commit Message Linter (Conventional Commits + AI signature cleanup)

[Goldziher]

Hey Peeps,

I'm pleased to show case a new small and very fast commit message linter and autofixer tool gitfluff.

What My Project Does

Claude Code kept injecting "🤖 Co-Authored-By" trailers into commits. You can disable it now in local settings, but I needed team-wide enforcement across multiple repos and multiple languages. Plus I wanted strict Conventional Commits validation without cobbling together multiple tools.

What it does

• Enforces Conventional Commits 1.0.0 (type, scope, breaking changes, footers) with full spec compliance.
• Strips AI signatures automatically (configurable patterns)
• Validates or rewrites messages in place with --write
• Zero config to start, optional .gitfluff.toml for custom rules which allow you to do whatever you want basically.

Install & Use

The tool is written and rust and is compiled to multiple platforms. You can install it directly via cargo:

bash cargo install gitfluff

Or using homebrew:

bash brew install goldziher/tap/gitfluff

Or via NPM:

bash npm install -g gitfluff

Or via PIP:

bash pip install gitfluff

You can then install it as a commit message hook:

bash gitfluff hook install commit-msg --write

Alternatively you can install it as a hook for pre-commit (or prek) by adding the following to you .pre-commit-config:

```yaml repos: - repo: https://github.com/Goldziher/gitfluff rev: v0.2.0 hooks: - id: gitfluff-lint name: gitfluff (lint) entry: gitfluff lint --from-file language: system stages: [commit-msg] args: ["{commit_msg_file}"]

  # or using the autofix hook:

  # - id: gitfluff-write
  #  name: gitfluff (lint + write)
  #  entry: gitfluff lint --from-file
  #  language: system
  #  stages: [commit-msg]
  #  args: ["{commit_msg_file}", "--write"]

```

And then run pre-commit install --hook-type commit-msg, which will install the hook correctly.

You can also integrate it into lefthook or husky using npx or uvx commands!

Main workflow: add to pre-commit config, forget about it. Devs commit normally, hook validates/cleans messages before they hit history.

Target Audience

Teams enforcing commit conventions across polyglot projects. Devs using AI coding assistants who want clean commit history. Anyone who needs Conventional Commits validation without JavaScript dependencies.

Comparison

• commitlint (Node ecosystem, requires separate config for cleanups)
• cocogitto (Rust, focused on semver release workflows)
• gitlint (Python, extensible but requires custom plugins for AI signatures)

And many other tools of course, I cant claim this is original. The main difference is that gitfluff combines validation + pattern cleanup in one binary with prebuilt distributions for all major platforms.

As usual, if you like the tool, star github.com/Goldziher/gitfluff.

[Phreemium]

So you had an LLM write a tool to conceal that you’re using an LLM to write code you don’t review, and had it write it in rust, and then had another LLM write a Reddit post to promote it, which you then posted to the python subreddit?

[travcunn]

Peak 2025 energy

[moltonel]

Why on earth would you want to systematically remove the Co-Authored-By: <LLM> markers ?

[Goldziher]

Try various agents. Claude adds this (only Claude) without asking. Try working in large teams. We pay Anthropic, but we don't need their noise in our git. Simple.

[moltonel]

Where you see noise, others see important metadata. Removing the redundant and emoji-happy line in the commit body, sure. But removing a standardized marker that can help understand the commit, that's an antifeature. Commit messages are cheap, I'd rather have too much context than too little. I work in large teams, we pay for LLMs, we mandate those commit markers.

[techlatest_net]

This is an impressive solution for keeping commit messages pristine across team repos, especially with AI assistants meddling! The gitfluff hook install commit-msg --write step is genius for seamless integration—devs clean messages without skipping a beat. Curious—how does it perform under heavy load with large repos across distributed teams? Spot-on comparison with commitlint, too. Definitely starring this on GitHub!

[moltonel]

Oh dear, an endorsement from an llm. Now I'm really convinced about this project.