React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
Agent skill
Conventional Commit Formatter
by maslennikov-ig in maslennikov-ig/claude-code-orchestrator-kit
Builds conventional commit messages from a type, optional scope, description and body, validates them and appends a Claude Code attribution footer.
Install Conventional Commit Formatter
$ npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill format-commit-message -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install maslennikov-ig/claude-code-orchestrator-kit format-commit-message --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/maslennikov-ig/claude-code-orchestrator-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/format-commit-message .claude/skills/format-commit-message && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "format-commit-message" agent skill from https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/format-commit-message into .claude/skills/format-commit-message/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "format-commit-message", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/format-commit-messageType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill format-commit-message -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install maslennikov-ig/claude-code-orchestrator-kit format-commit-message --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maslennikov-ig/claude-code-orchestrator-kit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/format-commit-message .agents/skills/format-commit-message && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "format-commit-message" agent skill from https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/format-commit-message into .agents/skills/format-commit-message/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "format-commit-message", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill format-commit-message -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install maslennikov-ig/claude-code-orchestrator-kit format-commit-message --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maslennikov-ig/claude-code-orchestrator-kit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/format-commit-message .cursor/skills/format-commit-message && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "format-commit-message" agent skill from https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/format-commit-message into .cursor/skills/format-commit-message/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "format-commit-message", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/maslennikov-ig/claude-code-orchestrator-kit.git --path .claude/skills/format-commit-message--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill format-commit-message -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install maslennikov-ig/claude-code-orchestrator-kit format-commit-message --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maslennikov-ig/claude-code-orchestrator-kit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/format-commit-message .gemini/skills/format-commit-message && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "format-commit-message" agent skill from https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/format-commit-message into .gemini/skills/format-commit-message/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "format-commit-message", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install maslennikov-ig/claude-code-orchestrator-kit format-commit-messageInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill format-commit-message -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/maslennikov-ig/claude-code-orchestrator-kit.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/format-commit-message .github/skills/format-commit-message && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "format-commit-message" agent skill from https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/format-commit-message into .github/skills/format-commit-message/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "format-commit-message", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill format-commit-message -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install maslennikov-ig/claude-code-orchestrator-kit format-commit-message --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maslennikov-ig/claude-code-orchestrator-kit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/format-commit-message .opencode/skills/format-commit-message && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "format-commit-message" agent skill from https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/format-commit-message into .opencode/skills/format-commit-message/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "format-commit-message", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
format-commit-message- GitHub stars
- 260
- Token cost
- ~1.1k tokens
- SKILL.md length
- 255 words
- Files
- 2
- Skills in repo
- 29
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Builds conventional commit messages from a type, optional scope, description and body, validates them and appends a Claude Code attribution footer.
- Works in 4 steps: Gather Commit Information → Format Message → Validate Message → …
- Writing a release commit with a consistent format
- SKILL.md covers When to Use, Instructions, Error Handling and Examples, plus 2 more sections
- Reaches claude.com
What it does
The skill takes a type (feat, fix, chore, docs, refactor, test, style or perf), an optional scope, a short description, an optional body and an optional breaking-change flag, and returns a message in the type, scope and description layout followed by the body and a footer. The footer is a Claude Code attribution line and a Co-Authored-By line, and a breaking change prepends BREAKING CHANGE to the body or footer.
Validation rejects unknown types, missing descriptions and descriptions of 72 characters or more, and expects lowercase descriptions with no trailing period, lowercase scopes and bodies wrapped at 72 characters. Each failure returns a specific error, such as listing the valid types or giving the character count. A template.md file sits alongside. It suits release commits, automated version bumps, refactors and documentation updates.
When your agent uses it
- Writing a release commit with a consistent format
- Generating commit messages for automated version bumps
- Checking that a message follows conventional commit rules
Example prompts
- “Write a feat commit for adding a dark mode toggle.”
- “Format a fix commit in the api scope about a connection pool memory leak, with a body.”
- “Mark this refactor commit as a breaking change and validate the message length.”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Gather Commit Information
- Format Message
- Validate Message
- Return Formatted Message
What it can do on your machine
Read from SKILL.md and the folder at commit 8c3b576. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
claude.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Conventional Commit Formatter loads about 1.1k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 255 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 255 words (~1,112 tokens).
“Generate conventional commit messages following project standards with proper attribution.”
- name
- format-commit-message
Files
SKILL.md and 1 other file in .claude/skills/format-commit-message of maslennikov-ig/claude-code-orchestrator-kit.
- SKILL.md
- template.md
Open the folder on GitHubat commit 8c3b576
Compare with similar skills
Conventional Commit Formatter next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Conventional Commit Formatter this skillmaslennikov-ig/claude-code-orchestrator-kit | 260 | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| ToolJet Multi-Repo CommitToolJet/ToolJet | 41k | — | ~1.3k | Automated safety check: Pass | AGPL-3.0 | |
| Git Workflow and Versioningaddyosmani/agent-skills | 103k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| React Router Pull Request Creatorremix-run/react-router | 57k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
ToolJet Multi-Repo Commit
ToolJet/ToolJet
Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.
Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
Saleor Commit Workflow
saleor/saleor
Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.
More from maslennikov-ig/claude-code-orchestrator-kit
All 29 skills in this repoSenior Architect Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin…
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
Senior Prompt Engineer
maslennikov-ig/claude-code-orchestrator-kit
Provides reference guides and Python scripts for prompt optimization, RAG evaluation, and agent orchestration when building or tuning LLM systems.
Priority Score Calculator
maslennikov-ig/claude-code-orchestrator-kit
Scores a bug, issue or task from severity, impact and likelihood on a 0-30 scale and maps the total to a P0 to P4 priority category with a suggested action.
Code Review with Beads Tasks
maslennikov-ig/claude-code-orchestrator-kit
Reviews staged changes, a branch, a PR or a path for bugs, security gaps and performance issues, then writes an evidence-based report and creates Beads tasks.
Semantic Version Parser
maslennikov-ig/claude-code-orchestrator-kit
Extracts and validates semantic version strings from mixed text, parsing major, minor, patch, prerelease and build components with a fixed regular expression.
Related
Works with
Categories
Questions about Conventional Commit Formatter
What does Conventional Commit Formatter do?
Builds conventional commit messages from a type, optional scope, description and body, validates them and appends a Claude Code attribution footer. The skill takes a type (feat, fix, chore, docs, refactor, test, style or perf), an optional scope, a short description, an optional body and an optional breaking-change flag, and returns a message in the type, scope and description layout followed by the body and a footer. The footer is a Claude Code attribution line and a Co-Authored-By line, and a breaking change prepends BREAKING CHANGE to the body or footer.
When should I use Conventional Commit Formatter?
Conventional Commit Formatter fits situations like: writing a release commit with a consistent format; generating commit messages for automated version bumps; checking that a message follows conventional commit rules.
How do I install Conventional Commit Formatter in Claude Code?
Run `npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill format-commit-message -a claude-code`. Or copy the skill folder (.claude/skills/format-commit-message in maslennikov-ig/claude-code-orchestrator-kit) into .claude/skills/format-commit-message in your project. Claude Code loads it when a task matches its description.
How do I install Conventional Commit Formatter in Codex?
Run `npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill format-commit-message -a codex`. Or copy the skill folder (.claude/skills/format-commit-message in maslennikov-ig/claude-code-orchestrator-kit) into .agents/skills/format-commit-message in your project. Codex loads it when a task matches its description.
Can I use Conventional Commit Formatter in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill format-commit-message -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/format-commit-message, .gemini/skills/format-commit-message, .github/skills/format-commit-message and .opencode/skills/format-commit-message in your project.
What does Conventional Commit Formatter need to run?
SKILL.md names no scripts, command-line tools or credentials: Conventional Commit Formatter is instructions for the agent only.
Does Conventional Commit Formatter access the network?
SKILL.md names 1 domain. In commands or code: claude.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Conventional Commit Formatter safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Conventional Commit Formatter use?
Conventional Commit Formatter has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Conventional Commit Formatter use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Conventional Commit Formatter?
Skills that share tags, products or a category with Conventional Commit Formatter: React Router Release Notes Prep (remix-run/react-router, 57k stars), ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 103k stars) and React Router Pull Request Creator (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Conventional Commit Formatter?
maslennikov-ig (a GitHub user) maintains it in maslennikov-ig/claude-code-orchestrator-kit, which has 260 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on March 5, 2026.
Source: maslennikov-ig/claude-code-orchestrator-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.