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.
Creates a commit that follows the project's COMMIT_GUIDELINES.md, choosing the type by what the change does and verifying the result.
Install Commit with Project Guidelines
$ npx skills add gittower/git-flow-next --skill commit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gittower/git-flow-next 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/gittower/git-flow-next.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/gittower/git-flow-next/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/gittower/git-flow-next/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 gittower/git-flow-next --skill commit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gittower/git-flow-next commit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gittower/git-flow-next.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/gittower/git-flow-next/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 gittower/git-flow-next --skill commit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gittower/git-flow-next commit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gittower/git-flow-next.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/gittower/git-flow-next/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/gittower/git-flow-next.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 gittower/git-flow-next --skill commit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gittower/git-flow-next commit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gittower/git-flow-next.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/gittower/git-flow-next/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 gittower/git-flow-next 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 gittower/git-flow-next --skill commit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gittower/git-flow-next.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/gittower/git-flow-next/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 gittower/git-flow-next --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 gittower/git-flow-next commit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gittower/git-flow-next.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/gittower/git-flow-next/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
- 458
- Token cost
- ~818 tokens
- SKILL.md length
- 353 words
- Files
- 1
- Skills in repo
- 25
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Creates a commit that follows the project's COMMIT_GUIDELINES.md, choosing the type by what the change does and verifying the result.
- Works in 6 steps: Read COMMIT_GUIDELINES.md for all… → Check Status → Analyze Changes → …
- Committing staged changes in a repository with commit guidelines
- SKILL.md covers Instructions, Commit Type Decision Guide, Hard Wrapping Technique and Example
- Calls git and go
What it does
The agent reads COMMIT_GUIDELINES.md first, checks `git status` and `git diff --cached`, and asks what to stage, or stages everything with `git add -A`, if nothing is staged. It reviews the diff, picks a commit type and scope per the guidelines, writes the message, creates the commit with a HEREDOC and then runs `git log -1` to check it.
A decision guide chooses the type by purpose rather than file type: feat, fix, refactor, test, docs, ci, build, style or chore. Pitfalls are called out: a Markdown file that configures tool behavior, such as Copilot instructions or Claude skills, is ci and not docs; fix is only for user-facing bugs, so a CI workflow fix is ci and a test fix is test. The skill also covers a hard-wrapping technique for message bodies.
When your agent uses it
- Committing staged changes in a repository with commit guidelines
- Choosing between feat, fix, ci, docs and test for a change
- Verifying a commit message after it is created
Example prompts
- “Commit my staged changes following COMMIT_GUIDELINES.md.”
- “Which commit type fits an update to our Claude skills file?”
- “Stage everything and commit with a properly scoped message.”
Requirements
- git
- A COMMIT_GUIDELINES.md file in the repository
- Pre-approved tools (allowed-tools): Bash, Read, Grep
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Read COMMIT_GUIDELINES.md for all formatting rules, commit types, and conventions
- Check Status
- Analyze Changes
- Write Commit Message per COMMIT_GUIDELINES.md rules
- Create Commit using HEREDOC format for proper formatting
- Verify — run git log -1 to check the message
What it can do on your machine
Read from SKILL.md and the folder at commit 00d1b4b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
BashReadGrep
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitgo
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
Commit with Project Guidelines loads about 818 tokens when it runs. Until then it costs about 13 tokens; SKILL.md has 353 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash, Read, Grep
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 353 words (~818 tokens).
“Create a well-formatted commit following the project's COMMIT_GUIDELINES.md.”
- name
- commit
- allowed-tools
- Bash, Read, Grep
- argument-hint
- optional message hint
Files
Just SKILL.md in .claude/skills/commit of gittower/git-flow-next.
Open the folder on GitHubat commit 00d1b4b
Compare with similar skills
Commit with Project Guidelines 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 |
|---|---|---|---|---|---|---|
| Commit with Project Guidelines this skillgittower/git-flow-next | 458 | — | ~818 | Automated safety check: Notes | Custom licence | |
| 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 gittower/git-flow-next
All 25 skills in this repoGitHub Issue Analysis
gittower/git-flow-next
Analyzes a GitHub issue for the git-flow-next project and writes an analysis document under .ai/ that covers the affected code and proposes TODO comments.
PR Review Feedback Handler
gittower/git-flow-next
Fetches review comments on a pull request, judges each one, writes the evaluation to a plan file and implements accepted changes, waiting for approval before anything public.
Stale PR Review Check
gittower/git-flow-next
Scans open pull requests against the project's review response window and reports which ones need action, read-only unless you approve a reminder.
Local Code Review
gittower/git-flow-next
Reviews local commits, branch diffs or pull requests against project guidelines and writes the result to local files, never posting it to GitHub.
Test-First Implementation Plan
gittower/git-flow-next
Builds a two-phase implementation plan from a spec issue, analysis or concept, writing a detailed test plan first and the implementation outline second.
Create Spec
gittower/git-flow-next
Create a Codex-gated spec issue from a triaged report, concept, or idea
Related
Works with
Categories
Questions about Commit with Project Guidelines
What does Commit with Project Guidelines do?
Creates a commit that follows the project's COMMIT_GUIDELINES.md, choosing the type by what the change does and verifying the result. md first, checks `git status` and `git diff --cached`, and asks what to stage, or stages everything with `git add -A`, if nothing is staged. It reviews the diff, picks a commit type and scope per the guidelines, writes the message, creates the commit with a HEREDOC and then runs `git log -1` to check it.
When should I use Commit with Project Guidelines?
Commit with Project Guidelines fits situations like: committing staged changes in a repository with commit guidelines; choosing between feat, fix, ci, docs and test for a change; verifying a commit message after it is created.
How do I install Commit with Project Guidelines in Claude Code?
Run `npx skills add gittower/git-flow-next --skill commit -a claude-code`. Or copy the skill folder (.claude/skills/commit in gittower/git-flow-next) into .claude/skills/commit in your project. Claude Code loads it when a task matches its description.
How do I install Commit with Project Guidelines in Codex?
Run `npx skills add gittower/git-flow-next --skill commit -a codex`. Or copy the skill folder (.claude/skills/commit in gittower/git-flow-next) into .agents/skills/commit in your project. Codex loads it when a task matches its description.
Can I use Commit with Project Guidelines 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 gittower/git-flow-next --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 Commit with Project Guidelines need to run?
Going by SKILL.md and its folder, Commit with Project Guidelines needs the command-line tools its instructions call (git and go). Our summary lists: git; A COMMIT_GUIDELINES.md file in the repository. Its frontmatter pre-approves these tools: Bash, Read, Grep.
Does Commit with Project Guidelines 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 Commit with Project Guidelines safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Commit with Project Guidelines use?
Commit with Project Guidelines 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 Commit with Project Guidelines use?
About 818 tokens (SKILL.md is roughly 3.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 Commit with Project Guidelines?
Skills that share tags, products or a category with Commit with Project Guidelines: 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 Commit with Project Guidelines?
gittower (a GitHub organization) maintains it in gittower/git-flow-next, which has 458 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on September 8, 2026.
Source: gittower/git-flow-next on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.