Samuel BertheCreator of Go library lo, 21k+ GitHub stars5,400 installs on skills.sh

Conventional Git

Conventional Commits v1.0.0 branch naming.

Use in my agent
Use Edge to load the skill conventional-git from samber/cc-skills for my task. If Edge is not set up, read getedge.cc/SKILL.md and ask me first.
Works in any agentClaude CodeCodexCursorClaude appChatGPT+ any other agent
samber/cc-skills
Security state: reviewed

2 static scans, 0 counted findings.

Edge checks it again each time your agent loads it.

SKILL.md2 files · 19.4 KB

From the samber public repository. Edge did not write or edit this skill.

What it does

  • Conventional Commits v1.0.0 branch naming, worktree naming, and commit message standards for GitHub and GitLab projects.
  • Use when creating branches, naming worktrees, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation.
  • Apply when your project needs consistent git history, SemVer-driven releases, parseable changelog generation, or automatic issue closing.
  • Trigger when the user asks how to name a worktree, create a git worktree, or organize worktrees alongside branches.
SB

Why Samuel Berthe

Go open source author. Each fact links its public source.

  • Created samber/lo, 21k+ stars

    His Lodash-style Go generics library lo has 21k+ GitHub stars.

    GitHub
  • Packaged in Ubuntu

    lo ships as an Ubuntu source package, golang-github-samber-lo.

    Ubuntu packages
  • 3k+ stars on his Go skills

    His Golang agent skills collection has 3k+ GitHub stars.

    GitHub

Public sources, checked Oct 26, 2026.

How it works

  1. 1
    Copy

    Try for free gives you one prompt.

  2. 2
    Paste

    Paste it into Claude Code, Codex or Cursor.

  3. 3
    Ask

    Ask for the outcome. Your agent loads Conventional Git.

Related skills

VT
Prd Worktree
vtmocanu

Create a git worktree for PRD work with a descriptive branch name. Infers PRD from context or asks user.

DA
Commit Work
davila7

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, stag

WS
Changelog Automation
wshobson

Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.

+175 installs this week
CS
Commit
casper-studios

Generate commit messages following conventional commits and commit staged changes. Use when creating commits or when user invokes /commit.

GI
Conventional Commit
github

Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, includi

+107 installs this week
GI
Git Commit
github

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 ty

+377 installs this week
Evidence

No evidence record yet

No measured run with and without this skill yet, so this page makes no performance claim. 2 static scans, 0 counted findings. Security state at 2026-11-17: reviewed. Static scans check the code, not how well the skill works.

State definitions

Skill details

Security scansReviewed

2 static scans, 0 counted findings. Security state at 2026-11-17: reviewed. Edge checks it again each time your agent loads it.

Edge static checks (Edge-run): edge-static/1.0.2. Scope: Static patterns for remote execution, credentials with network sends, obfuscation, prompt overrides, hidden Unicode, binaries and persistence. Raw findings: not supplied.

Edge committed-secret checks (Edge-run): edge-secrets/1.0.0. Scope: Credentials committed in the skill's files (values never shown). Raw findings: not supplied.

Socket (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.

Snyk (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.

Edge static checks
Pass · 0 counted findings · 2026-11-17
Edge committed-secret checks
Pass · 0 counted findings · 2026-11-17
Creator, source & licencesamber

From the samber public repository. Edge did not write or edit this skill.

Revision
f6dad7c07bad369d25912cfa9f0b21790f431066
Package hash
sha256:1c04fb66b4b67879598e8065f2c3661661be986cdca4e29ece28db0fd4c59750
Licence
MIT
Description
Conventional Commits v1.0.0 branch naming, worktree naming, and commit message standards for GitHub and GitLab projects. Use when creating branches, naming worktrees, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation. Apply when your project needs consistent git history, SemVer-driven releases, parseable changelog generation, or automatic issue closing. Trigger when the user asks how to name a worktree, create a git worktree, or organize worktrees alongside branches.
Quoted from the skill’s own description
Read skill files2 files

2 files, 19.4 KB at revision f6dad7c07bad.

Questions about Conventional Git

What does Conventional Git do?

Conventional Commits v1.0.0 branch naming. Published by Samuel Berthe (samber/cc-skills).

Is Conventional Git safe to use?

Edge security state: Reviewed (2 Edge-run static scans, scanned Nov 17, 2026). The Evidence tab shows the scan.

How do I use Conventional Git in Claude Code, Codex or Cursor?

Click Try for free, pick your agent and follow its one step. Edge is free, with no Edge account.