Skip to main content
skill CX Codex

conventional-commits · tigrisdata — Claude Code skill: what it does, how to install

Enforces the Conventional Commits specification, adds AI tool attribution, and applies signoff flags for standardized git workflows.

MIT 105 installs ★ 2 updated 2026-07-23

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add tigrisdata/skills --skill conventional-commits -a claude-code
Open on GitHub

What conventional-commits does

This skill instructs coding agents to format every commit message according to the Conventional Commits standard. It maps permitted commit types such as feat, fix, docs, and chore directly to semantic version bumps. Descriptions must stay concise, lowercase, and in the imperative mood without trailing periods, while body text wraps at 72 characters to keep git logs readable.

Every commit created under these rules requires the --signoff flag to verify compliance with the Developer Certificate of Origin. The instructions also enforce AI attribution in the commit footer through Assisted-by: [Model Name] via [Tool Name], alongside issue closing tags and BREAKING CHANGE: indicators.

What it helps with

  • format commit messages according to Conventional Commits standards
  • mark breaking changes for automated semantic version bumping
  • attribute AI model contributions inside the commit footer
  • sign off commits with DCO trailers using the git signoff flag

Example prompts for the agent

  • Commit these changes to the auth module with a fix for the null response bug
  • Prepare a commit message for refactoring error handlers in the core package
  • Create a commit for the breaking API update in storage and link issue 123

How to install conventional-commits

1Skills CLI (Vercel)

npx skills add tigrisdata/skills --skill conventional-commits -a claude-code

2Manually: put the files in place

~/.claude/skills/conventional-commits/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/conventional-commits/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about conventional-commits

How to install conventional-commits in Claude Code?

Run npx skills add tigrisdata/skills --skill conventional-commits -a claude-code in your terminal. The skill file is placed at ~/.claude/skills/conventional-commits/SKILL.md.

What does conventional-commits do?

It guides the agent to write consistent git commit messages using strict types, optional scopes, 72-character body line wrapping, and proper breaking change notations.

Why does this skill require git signoff?

The skill mandates the --signoff flag on git commit to certify developer origin compliance by appending a Signed-off-by trailer to each change.

Source text

SKILL.md · MIT
---
name: conventional-commits
description: Use when creating git commits, writing commit messages, or following version control workflows
---

# Conventional Commits

Structured commit message format for version control that provides clear, readable project history.

## Overview

The Conventional Commits specification provides:

- **Automated changelog generation** - Tools can parse commits to generate CHANGELOG.md
- **Semantic versioning** - Commit types map to version bumps (feat → minor, breaking → major)
- **Clear project history** - Standardized format makes git log readable
- **Automated releases** - CI/CD can trigger releases based on commit types

## Quick Reference

| Type | Use For | Version Bump |
| ---- | ------- | ------------ |
| `feat` | New feature | MINOR |
| `fix` | Bug fix | PATCH |
| `docs` | Documentation only | PATCH |
| `style` | Formatting, no logic change | PATCH |
| `refactor` | Code restructuring, no behavior change | PATCH |
| `perf` | Performance improvement | PATCH |
| `test` | Adding or updating tests | PATCH |
| `build` | Build system or dependencies | PATCH |
| `ci` | CI/CD configuration | PATCH |
| `chore` | Maintenance, no user-facing change | PATCH |
| `revert` | Revert a previous commit | PATCH |

## Format

```text
<type>[optional scope]: <description>

[optional body]

[optional footer(s)]
```

**Rules:**

- Type is required
- Scope is optional - use parenthesized section affected: `(api)`, `auth)`, `parser)`
- Description is required
- Keep description concise, imperative mood, lowercase, no trailing period
- Body and footer are optional
- Separate subject from body with blank line
- Wrap body at 72 characters

## Examples

```text
feat: add user authentication

Implement JWT-based authentication with login/logout endpoints.
Includes password hashing and session management.

Closes: #123
```

```text
fix(api): handle null response from server

Previous implementation crashed when server returned null.
Now returns empty result set.

Assisted-by: GLM 4.6 via Claude Code
```

```text
feat(storage)!: change bucket listing API

BREAKING CHANGE: bucket list now returns async iterator
instead of array. Update all callers to use for-await.
```

```text
refactor(core): simplify error handling

Consolidate duplicate error handlers into single utility.
No behavior changes - internal cleanup only.
```

```text
revert: feat(auth): add OAuth support

This reverts commit 8b5a1c2. OAuth provider changed
their API and we need to redesign integration.
```

## Breaking Changes

Indicate breaking changes in two ways:

**Option 1**: Add `!` after type/scope

```text
feat(api)!: remove deprecated endpoint
```

**Option 2**: Add `BREAKING CHANGE:` footer

```text
feat(api): remove deprecated endpoint

BREAKING CHANGE: endpoint no longer exists. Use newEndpoint instead.
```

## AI Attribution

AI agents must disclose their assistance in the commit footer:

```text
Assisted-by: [Model Name] via [Tool Name]
```

Examples:

- `Assisted-by: GLM 4.6 via Claude Code`
- `Assisted-by: Claude Opus 4.5 via claude.ai`

## Common Mistakes

| Mistake | Why Wrong | Correct |
| ------- | --------- | ------- |
| `Added login feature` | Past tense, capitalized | `feat: add login feature` |
| `fix bug.` | Trailing period | `fix: resolve login error` |
| `update` | Missing type | `chore: update dependencies` |
| `feature:add-auth` | Missing space after colon | `feat: add authentication` |
| `FEAT: big change` | Uppercase type | `feat: add authentication` |
| Multi-line description no blank line | No separation | Add blank line after subject |

## Body Guidelines

- **What**: Motivation for the change (vs. code comments describe HOW)
- **Contrast**: Explain the WHY and WHAT, not code details
- **Wrap at 72 characters** for readability in git log

```text
feat(summarization): add support for nested bullet points

Previous implementation only flattened all content. Now preserves
hierarchy by respecting indentation levels. Users can now create
structured summaries with parent-child relationships.

Closes: #456
```

## Footer Guidelines

Use footers for:

- **Breaking changes**: `BREAKING CHANGE: detailed explanation`
- **Issue references**: `Closes: #123`, `Fixes: #456`, `Refs: #789`
- **AI attribution**: `Assisted-by: Model via Tool`

Multiple footers separated by blank lines:

```text
feat: add batch upload

Implements multipart upload for large files.

BREAKING CHANGE: upload() signature changed - now requires options object
Closes: #123
Assisted-by: GLM 4.6 via Claude Code
```

## Git Commit Flags

**Required flag:** Always use `--signoff` when committing:

```bash
git commit --signoff -m "feat: add user authentication"
```

The `--signoff` flag adds a `Signed-off-by` trailer to the commit message, indicating the committer has certified the commit follows developer certificate of origin (DCO).

## Testing Your Commit

Before committing, verify:

1. [ ] Type is from allowed list
2. [ ] Description is imperative mood (add, fix, update)
3. [ ] Description is lowercase
4. [ ] No trailing period on description
5. [ ] Breaking changes marked with `!` or footer
6. [ ] AI attribution included (if applicable)
7. [ ] Body explains WHY not HOW
8. [ ] Using `--signoff` flag

© tigrisdata · MIT · tigrisdata/skills

Similar skills

All skills for Git and GitHub →

conventional-commits by other authors comes first.

conventional-commits patricio0312rev The skill writes commit messages to the Conventional Commits spec: type, scope, body and footers. Useful when you want automated versioning and changelogs. CX Codex +1 504installs atomic-commits Rohit Ghumare Enforces Git best practices: atomic commits in Conventional Commits format, mandatory feature branches, and selective file staging. CX Codex +1 ★ 2,966repo stars commits itechmeat This skill guides agents in writing Conventional Commits and marking breaking changes. Use it when commit history feeds changelogs or SemVer. CX Codex +1 178installs conventional-commit-message dangreen conventional-commit-message generates changelog-ready commit messages following Conventional Commits 1.0.0 and conventional-changelog presets. It guides AI agents on type selection and breaking changes. CX Codex +1 1,100installs smart-commit rohitg00 The smart-commit plugin for Claude Code analyzes code changes and creates Conventional Commits messages. It also generates changelogs. ★ 2,858repo stars conventional-git samber conventional-git enforces Conventional Commits v1.0.0 rules for branch names and commit messages. Useful for parseable git history and automated changelogs on GitHub and GitLab. CX Codex +1 5,400installs conventional-commit official github A GitHub Copilot skill that builds commit messages in the Conventional Commits format. After you change files, it checks the diff and commits with a message assembled from an XML template. CX Codex +1 17,103installs

From the same set11

The whole set →
tigris-agent-kit tigris-agent-kit — a skill for Tigris object storage workflows: isolated dataset forks, per-agent buckets with TTL, snapshots and bucket webhooks. CX Codex +1 3,800installs tigris-s3-migration tigris-s3-migration — a skill that walks an object-storage migration from AWS S3, GCS or Azure Blob to Tigris. Useful when a bucket has to switch over without taking production down. CX Codex +1 3,800installs tigris-static-assets tigris-static-assets deploys static assets to Tigris object storage for global CDN delivery, configuring Cache-Control headers and build pipelines across web frameworks. CX Codex +1 3,800installs tigris-image-optimization tigris-image-optimization — a skill for images stored in Tigris: it builds variants at upload time, serves them from a public bucket and points you to the right framework guide. CX Codex +1 3,800installs tigris-sdk-guide tigris-sdk-guide tells your agent which Tigris SDK or CLI to reach for: native packages for TypeScript, Go and Python, AWS-compatible clients for Ruby and PHP. CX Codex +1 3,800installs file-storage file-storage helps configure Tigris Object Storage buckets via CLI and handle file uploads in Node.js, Rails, or Laravel. CX Codex +1 3,800installs tigris-snapshots-forking tigris-snapshots-forking — a skill for Claude Code, Codex, Cursor and other agents that takes Tigris bucket snapshots and forks them into isolated copies. Deletions inside a fork leave the source bucket untouched. CX Codex +1 453installs tigris-bucket-management tigris-bucket-management manages Tigris Storage buckets lifecycle, including creation, listing with pagination, status inspection, and safe deletion. CX Codex +1 135installs

Project sponsors

Companies that keep this analytics open