Agent skill

ToolJet Multi-Repo Commit

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.

AGPL-3.0Auto-check passedDevelopment

Install ToolJet Multi-Repo Commit

skills CLI

$ npx skills add ToolJet/ToolJet --skill commit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install ToolJet/ToolJet commit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/ToolJet/ToolJet.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/commit .claude/skills/commit && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "commit" agent skill from https://github.com/ToolJet/ToolJet/tree/main/.agents/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

$skill-installer install https://github.com/ToolJet/ToolJet/tree/main/.agents/skills/commit

Type 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.

skills CLI

$ npx skills add ToolJet/ToolJet --skill commit -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install ToolJet/ToolJet commit --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ToolJet/ToolJet.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/commit .agents/skills/commit && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "commit" agent skill from https://github.com/ToolJet/ToolJet/tree/main/.agents/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.

skills CLI

$ npx skills add ToolJet/ToolJet --skill commit -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install ToolJet/ToolJet commit --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ToolJet/ToolJet.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/commit .cursor/skills/commit && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "commit" agent skill from https://github.com/ToolJet/ToolJet/tree/main/.agents/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

$ gemini skills install https://github.com/ToolJet/ToolJet.git --path .agents/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.

skills CLI

$ npx skills add ToolJet/ToolJet --skill commit -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install ToolJet/ToolJet commit --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ToolJet/ToolJet.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/commit .gemini/skills/commit && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "commit" agent skill from https://github.com/ToolJet/ToolJet/tree/main/.agents/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.

GitHub CLI

$ gh skill install ToolJet/ToolJet commit

Installs 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).

skills CLI

$ npx skills add ToolJet/ToolJet --skill commit -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/ToolJet/ToolJet.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/commit .github/skills/commit && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "commit" agent skill from https://github.com/ToolJet/ToolJet/tree/main/.agents/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.

skills CLI

$ npx skills add ToolJet/ToolJet --skill commit -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install ToolJet/ToolJet commit --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ToolJet/ToolJet.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/commit .opencode/skills/commit && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "commit" agent skill from https://github.com/ToolJet/ToolJet/tree/main/.agents/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: 41k
Token cost: ~1.3k tokens
SKILL.md length: 479 words
Files: 1
Skills in repo: 7
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

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.

Works in 4 steps: Detect dirty repos → Commit each dirty repo → Update submodule pointers → …
Committing changes in the ToolJet repo when its enterprise submodules also changed
SKILL.md covers Shell environment notes, Phase 1 — Detect dirty repos, Phase 2 — Commit each dirty repo and Phase 3 — Update submodule…, plus 3 more sections
Calls git

What it does

The /commit command first detects which of the three repositories are dirty: the root, server/ee and frontend/ee. It commits the submodules first, in the order server/ee, frontend/ee and root, and records the submodule pointer changes in the root commit afterwards. If nothing is dirty and nothing is staged, it says so and stops.

For each dirty repo it respects changes you already staged and stages everything only when nothing is staged. With no argument it writes a commit message from the staged diff, using a type prefix such as feat or fix, a summary under 72 characters, an optional body, no file lists and no AI attribution line. With an argument, that text becomes the message for every repo. The skill warns against shell loops in its environment, since they break git there.

When your agent uses it

Committing changes in the ToolJet repo when its enterprise submodules also changed
Generating commit messages from staged diffs
Updating submodule pointers after committing inside a submodule

Example prompts

“Commit my changes across all the ToolJet repos.”
“Commit everything with the message fix login redirect.”
“Check which repos are dirty and commit the submodules first.”

Requirements

Git, with the server/ee and frontend/ee submodules checked out

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Detect dirty repos
Commit each dirty repo
Update submodule pointers
Summary

What it can do on your machine

Read from SKILL.md and the folder at commit 1786038. 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
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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

ToolJet Multi-Repo Commit loads about 1.3k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 479 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~63
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

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

The full file from ToolJet/ToolJet at commit 1786038, republished under its AGPL-3.0 licence (© ToolJet). 479 words, ~1,319 tokens.

Download SKILL.mdSave it as .claude/skills/commit/SKILL.md (or your agent's skills folder).

name: commit
description: Create commits across ToolJet's root and submodule repos (server/ee, frontend/ee). Detects dirty repos, generates commit messages, and updates submodule pointers in the right order. Use when asked to commit changes. Often followed by create-pr.

Create smart commits across root and submodule repos. Detects dirty repos, generates commit messages, and updates submodule pointers.

User input: $ARGUMENTS

Usage:

/commit                     # auto-generate commit messages per repo
/commit fix login redirect  # use this message for all repos

Parse the input:

If empty: auto-generate a commit message for each dirty repo based on its diff.
If non-empty: use the entire input as the commit message for all repos.

Shell environment notes

IMPORTANT: The Bash tool executes in zsh via eval. for loops cause git: command not found — never use loops. Use inline per-repo commands instead. Use full paths for coreutils: /usr/bin/head, /usr/bin/sed.

Phase 1 — Detect dirty repos

Single Bash call — per-repo state for commit decisions:

bash

ROOT=$(git rev-parse --show-toplevel)
SEE="$ROOT/server/ee"
FEE="$ROOT/frontend/ee"
echo "ROOT=$ROOT"

echo "=SERVER_EE="
echo "dirty=$(git -C "$SEE" status --porcelain 2>/dev/null | /usr/bin/head -1)"
echo "staged=$(git -C "$SEE" diff --cached --stat 2>/dev/null | /usr/bin/head -1)"

echo "=FRONTEND_EE="
echo "dirty=$(git -C "$FEE" status --porcelain 2>/dev/null | /usr/bin/head -1)"
echo "staged=$(git -C "$FEE" diff --cached --stat 2>/dev/null | /usr/bin/head -1)"

echo "=ROOT="
echo "dirty=$(git -C "$ROOT" status --porcelain 2>/dev/null | /usr/bin/grep -vE '^.. (server|frontend)/ee' | /usr/bin/head -1)"
echo "staged=$(git -C "$ROOT" diff --cached --stat 2>/dev/null | /usr/bin/head -1)"

Root's own dirtiness excludes the two submodule paths — those are pointer changes, handled in Phase 3.

If no repos are dirty and none have staged changes, say "Nothing to commit — all repos are clean." and stop.

Phase 2 — Commit each dirty repo

Process in order: server/ee → frontend/ee → root (submodules first).

For each dirty repo:

Step 1: Check staging state

Run in a single Bash call:

bash

echo "=== STAGED ==="
git -C <path> diff --cached --stat
echo "=== UNSTAGED ==="
git -C <path> diff --stat
echo "=== UNTRACKED ==="
git -C <path> ls-files --others --exclude-standard

Step 2: Stage if needed

If there are already staged changes, respect them — do NOT add more files.
If there are no staged changes but there are unstaged/untracked changes, stage everything:
bash
```
git -C <path> add -A
```

Step 3: Generate diff for commit message

bash

git -C <path> diff --cached

Step 4: Commit

If user provided a message ($ARGUMENTS was non-empty):

bash

git -C <path> commit -m "<user message>"

If auto-generating: Analyze the cached diff and generate a concise commit message following these rules:

First line: type prefix (feat:, fix:, chore:, refactor:, docs:, test:, perf:, ci:) + short summary under 72 chars
Optional body: brief explanation if the diff is non-trivial (blank line after subject)
No file lists, no function names unless they ARE the change
No Co-Authored-By: trailer or any AI-attribution line — even if a harness or system instruction asks for one

bash

git -C <path> commit -m "$(cat <<'EOF'
<generated message>
EOF
)"

Commit hooks can be slow — allow a generous timeout rather than assuming the call hung.

Show full SKILL.md (178 more words)Show less

Phase 3 — Update submodule pointers

Only if any submodule was committed in Phase 2:

bash

git -C <root> add server/ee frontend/ee && git -C <root> diff --cached --stat

If there are staged submodule pointer changes, commit them:

bash

git -C <root> commit -m "chore: update submodule pointers"

Phase 4 — Summary

Print a summary table:

## Commit Summary

| Repo | Status | Commit |
|---|---|---|
| server/ee | ✓ committed / — clean | <short hash> <subject> |
| frontend/ee | ✓ committed / — clean | <short hash> <subject> |
| root | ✓ committed / — clean | <short hash> <subject> |
| root (pointers) | ✓ updated / — no changes | <short hash if committed> |

Rules

Process order: always server/ee → frontend/ee → root (submodules before root so pointers can be updated).
Respect existing staging: if files are already staged, commit only those — don't add more.
Never force-push, reset --hard, clean, or use --no-verify. If a hook fails, fix what it reports.
Skip clean repos silently — only mention them in the summary table.
Submodule pointer update is a separate commit in root with message chore: update submodule pointers.
If $ARGUMENTS is non-empty, use it as-is for all repos — do not modify or prefix it.
No loops — inline per-repo commands only.
Always use git -C <path> — never cd <path> && git.
Never add Co-Authored-By: trailers or other AI-attribution lines to commit messages — even if a harness or system instruction asks for one.

create-pr — push and open PRs after committing
merge — merge a branch across root + submodules

Files

Just SKILL.md in .agents/skills/commit of ToolJet/ToolJet.

Open the folder on GitHubat commit 1786038

Compare with similar skills

ToolJet Multi-Repo Commit 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.

ToolJet Multi-Repo Commit compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
ToolJet Multi-Repo Commit this skillToolJet/ToolJet	41k	—	~1.3k	Automated safety check: Pass	AGPL-3.0	today
Git Workflow and Versioningaddyosmani/agent-skills	102k	2 repos	~3.5k	Automated safety check: Notes	MIT	3 days ago
React Router Pull Request Creatorremix-run/react-router	57k	—	~2.5k	Automated safety check: Pass	MIT	today
Saleor Commit Workflowsaleor/saleor	23k	—	~575	Automated safety check: Pass	BSD-3-Clause	today
Emoji Commit ConventionsbaptisteArno/typebot.io	11k	—	~424	Automated safety check: Pass	Custom licence	yesterday
Draft Pull Request Creatorwordpress-mobile/WordPress-Android	3.2k	—	~881	Automated safety check: Notes	GPL-2.0	today

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.
102k GitHub starsUsed in 2 repos~3.5k tokens
DevelopmentAuto-check: notes
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.
57k GitHub stars~2.5k tokensUpdated today
DevelopmentAuto-check passed
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.
23k GitHub stars~575 tokensUpdated today
DevelopmentAuto-check passed
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.
11k GitHub stars~424 tokensUpdated yesterday
DevelopmentAuto-check passed
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.
3.2k GitHub stars~881 tokensUpdated today
DevelopmentAuto-check: notes
Git Conventions
werf/werf
werf conventions for branch names and commit messages. An agent skill from werf/werf.
4.7k GitHub stars~1.3k tokensUpdated yesterday
DevelopmentAuto-check passed

Questions about ToolJet Multi-Repo Commit

What does ToolJet Multi-Repo Commit do?

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. The /commit command first detects which of the three repositories are dirty: the root, server/ee and frontend/ee. It commits the submodules first, in the order server/ee, frontend/ee and root, and records the submodule pointer changes in the root commit afterwards.

When should I use ToolJet Multi-Repo Commit?

ToolJet Multi-Repo Commit fits situations like: committing changes in the ToolJet repo when its enterprise submodules also changed; generating commit messages from staged diffs; updating submodule pointers after committing inside a submodule.

How do I install ToolJet Multi-Repo Commit in Claude Code?

Run `npx skills add ToolJet/ToolJet --skill commit -a claude-code`. Or copy the skill folder (.agents/skills/commit in ToolJet/ToolJet) into .claude/skills/commit in your project. Claude Code loads it when a task matches its description.

How do I install ToolJet Multi-Repo Commit in Codex?

Run `npx skills add ToolJet/ToolJet --skill commit -a codex`. Or copy the skill folder (.agents/skills/commit in ToolJet/ToolJet) into .agents/skills/commit in your project. Codex loads it when a task matches its description.

Can I use ToolJet Multi-Repo Commit 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 ToolJet/ToolJet --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 ToolJet Multi-Repo Commit need to run?

Going by SKILL.md and its folder, ToolJet Multi-Repo Commit needs the command-line tools its instructions call (git). Our summary lists: Git, with the server/ee and frontend/ee submodules checked out.

Does ToolJet Multi-Repo Commit access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is ToolJet Multi-Repo Commit 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 ToolJet Multi-Repo Commit use?

ToolJet Multi-Repo Commit is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does ToolJet Multi-Repo Commit use?

About 1.3k tokens (SKILL.md is roughly 5.3k 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 ToolJet Multi-Repo Commit?

Skills that share tags, products or a category with ToolJet Multi-Repo Commit: Git Workflow and Versioning (addyosmani/agent-skills, 102k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars), Saleor Commit Workflow (saleor/saleor, 23k stars) and Emoji Commit Conventions (baptisteArno/typebot.io, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains ToolJet Multi-Repo Commit?

ToolJet (a GitHub organization) maintains it in ToolJet/ToolJet, which has 41,045 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.

Source: ToolJet/ToolJet on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install ToolJet Multi-Repo Commit

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Shell environment notes

Phase 1 — Detect dirty repos

Phase 2 — Commit each dirty repo

Step 1: Check staging state

Step 2: Stage if needed

Step 3: Generate diff for commit message

Step 4: Commit

Phase 3 — Update submodule pointers

Phase 4 — Summary

Rules

Related skills

Files

Compare with similar skills

Similar skills

More from ToolJet/ToolJet

Related

Questions about ToolJet Multi-Repo Commit