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.
Reviews the working tree and creates a focused commit with a Conventional Commits message, staging selectively and never bypassing hooks.
Install Conventional Commit Writer
$ npx skills add EverMind-AI/EverOS --skill commit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install EverMind-AI/EverOS commit --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/EverMind-AI/EverOS.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/commit .claude/skills/commit && 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 "commit" agent skill from https://github.com/EverMind-AI/EverOS/tree/main/.claude/skills/commit into .claude/skills/commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit", 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/EverMind-AI/EverOS/tree/main/.claude/skills/commitType 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 EverMind-AI/EverOS --skill commit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install EverMind-AI/EverOS commit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EverMind-AI/EverOS.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/commit .agents/skills/commit && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "commit" agent skill from https://github.com/EverMind-AI/EverOS/tree/main/.claude/skills/commit into .agents/skills/commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit", 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 EverMind-AI/EverOS --skill commit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install EverMind-AI/EverOS commit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EverMind-AI/EverOS.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/commit .cursor/skills/commit && 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 "commit" agent skill from https://github.com/EverMind-AI/EverOS/tree/main/.claude/skills/commit into .cursor/skills/commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit", 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/EverMind-AI/EverOS.git --path .claude/skills/commit--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 EverMind-AI/EverOS --skill commit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install EverMind-AI/EverOS commit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EverMind-AI/EverOS.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/commit .gemini/skills/commit && 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 "commit" agent skill from https://github.com/EverMind-AI/EverOS/tree/main/.claude/skills/commit into .gemini/skills/commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit", 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 EverMind-AI/EverOS commitInstalls 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 EverMind-AI/EverOS --skill commit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/EverMind-AI/EverOS.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/commit .github/skills/commit && 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 "commit" agent skill from https://github.com/EverMind-AI/EverOS/tree/main/.claude/skills/commit into .github/skills/commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit", 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 EverMind-AI/EverOS --skill commit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install EverMind-AI/EverOS commit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EverMind-AI/EverOS.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/commit .opencode/skills/commit && 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 "commit" agent skill from https://github.com/EverMind-AI/EverOS/tree/main/.claude/skills/commit into .opencode/skills/commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit", 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
commit- GitHub stars
- 13k
- Token cost
- ~443 tokens
- SKILL.md length
- 197 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Reviews the working tree and creates a focused commit with a Conventional Commits message, staging selectively and never bypassing hooks.
- Works in 6 steps: Run git status and git diff (and git… → Review recent history for style: git log… → Group the change into a single focused… → …
- Committing the current change with a properly formatted message
- SKILL.md covers Steps, Types and Notes
- Calls git
What it does
The skill looks at `git status`, `git diff` and the staged diff, then recent history for style, and groups the change into one focused commit, staging selectively when unrelated work is mixed in. The message follows the Conventional Commits form of type, optional scope, optional breaking-change marker and an imperative summary, with an optional body explaining what and why.
A type table lists feat, fix, refactor, test, docs, style, perf, chore, build, ci and revert. Rules say to never use `--no-verify`, to fix the cause when a pre-commit hook fails, and to keep secrets, generated artifacts and work in progress off the protected main branch. The format is enforced by gitlint in the commit-msg hook, titles carry no emoji, and each commit holds one logical change so history stays bisectable.
When your agent uses it
- Committing the current change with a properly formatted message
- Splitting mixed edits into separate focused commits
- Marking a commit as a breaking change
Example prompts
- “Commit my changes with a Conventional Commits message.”
- “My working tree mixes a bug fix and a refactor. Split them into two commits.”
- “Write a commit for the search feature with the scope set and a breaking change marker.”
Requirements
- Git
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Run git status and git diff (and git diff --staged) to see what changed.
- Review recent history for style: git log --oneline -10.
- Group the change into a single focused commit. If the working tree mixes
- Write the message in Conventional Commits form
- Never use --no-verify. If pre-commit hooks fail, fix the cause and re-commit.
- Do not commit secrets, generated artifacts, or work-in-progress directly to
What it can do on your machine
Read from SKILL.md and the folder at commit d2aa949. 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
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
conventionalcommits.org
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 Writer loads about 443 tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 197 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
GitHub didn't answer just now, so the file isn't shown here. It has 197 words (~443 tokens).
- name
- commit
Files
Just SKILL.md in .claude/skills/commit of EverMind-AI/EverOS.
Open the folder on GitHubat commit d2aa949
Compare with similar skills
Conventional Commit Writer 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 Writer this skillEverMind-AI/EverOS | 13k | — | ~443 | Automated safety check: Pass | Apache-2.0 | |
| ToolJet Multi-Repo CommitToolJet/ToolJet | 41k | — | ~1.3k | Automated safety check: Pass | AGPL-3.0 | |
| Git Workflow and Versioningaddyosmani/agent-skills | 102k | 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 | |
| Saleor Commit Workflowsaleor/saleor | 23k | — | ~575 | Automated safety check: Pass | BSD-3-Clause | |
| Emoji Commit ConventionsbaptisteArno/typebot.io | 11k | — | ~424 | Automated safety check: Pass | Custom licence |
Similar skills
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.
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.
Emoji Commit Conventions
baptisteArno/typebot.io
Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.
Draft Pull Request Creator
wordpress-mobile/WordPress-Android
Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.
More from EverMind-AI/EverOS
Add Memory Kind
EverMind-AI/EverOS
Walks through adding a new persisted memory kind to EverOS: choose storage among Markdown, SQLite and LanceDB, pick a Markdown strategy, then wire schemas, repos and writers.
EverOS Release Workflow
EverMind-AI/EverOS
Walks through cutting a versioned everos release: bump the version, update the changelog, tag it, and review the drafted GitHub Release page before publishing.
New Branch from Main
EverMind-AI/EverOS
Creates a Git branch from an up-to-date main using a type-prefixed, kebab-case name such as feat or fix, and keeps work off main.
Pull Request with Project Template
EverMind-AI/EverOS
Opens a GitHub pull request against main with the gh CLI, after local checks pass and with the project's PR template filled in honestly.
Related
Works with
Categories
Questions about Conventional Commit Writer
What does Conventional Commit Writer do?
Reviews the working tree and creates a focused commit with a Conventional Commits message, staging selectively and never bypassing hooks. The skill looks at `git status`, `git diff` and the staged diff, then recent history for style, and groups the change into one focused commit, staging selectively when unrelated work is mixed in. The message follows the Conventional Commits form of type, optional scope, optional breaking-change marker and an imperative summary, with an optional body explaining what and why.
When should I use Conventional Commit Writer?
Conventional Commit Writer fits situations like: committing the current change with a properly formatted message; splitting mixed edits into separate focused commits; marking a commit as a breaking change.
How do I install Conventional Commit Writer in Claude Code?
Run `npx skills add EverMind-AI/EverOS --skill commit -a claude-code`. Or copy the skill folder (.claude/skills/commit in EverMind-AI/EverOS) into .claude/skills/commit in your project. Claude Code loads it when a task matches its description.
How do I install Conventional Commit Writer in Codex?
Run `npx skills add EverMind-AI/EverOS --skill commit -a codex`. Or copy the skill folder (.claude/skills/commit in EverMind-AI/EverOS) into .agents/skills/commit in your project. Codex loads it when a task matches its description.
Can I use Conventional Commit Writer 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 EverMind-AI/EverOS --skill commit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commit, .gemini/skills/commit, .github/skills/commit and .opencode/skills/commit in your project.
What does Conventional Commit Writer need to run?
Going by SKILL.md and its folder, Conventional Commit Writer needs the command-line tools its instructions call (git). Our summary lists: Git.
Does Conventional Commit Writer access the network?
SKILL.md names 1 domain. As links in the text: conventionalcommits.org. This is read from the text; nothing was executed.
Is Conventional Commit Writer 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 Writer use?
Conventional Commit Writer is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Conventional Commit Writer use?
About 443 tokens (SKILL.md is roughly 1.8k 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 Writer?
Skills that share tags, products or a category with Conventional Commit Writer: ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 102k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars) and Saleor Commit Workflow (saleor/saleor, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Conventional Commit Writer?
EverMind-AI (a GitHub organization) maintains it in EverMind-AI/EverOS, which has 13,351 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 6, 2026.
Source: EverMind-AI/EverOS on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.