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 Conventions: Guidelines for commit messages, branch naming, and version control practices
Install Git Conventions
$ npx skills add deadlock-mod-manager/deadlock-mod-manager --skill git-conventions -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install deadlock-mod-manager/deadlock-mod-manager git-conventions --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/deadlock-mod-manager/deadlock-mod-manager.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/git-conventions .claude/skills/git-conventions && 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 "git-conventions" agent skill from https://github.com/deadlock-mod-manager/deadlock-mod-manager/tree/main/.agents/skills/git-conventions into .claude/skills/git-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-conventions", 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/deadlock-mod-manager/deadlock-mod-manager/tree/main/.agents/skills/git-conventionsType 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 deadlock-mod-manager/deadlock-mod-manager --skill git-conventions -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install deadlock-mod-manager/deadlock-mod-manager git-conventions --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deadlock-mod-manager/deadlock-mod-manager.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/git-conventions .agents/skills/git-conventions && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "git-conventions" agent skill from https://github.com/deadlock-mod-manager/deadlock-mod-manager/tree/main/.agents/skills/git-conventions into .agents/skills/git-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-conventions", 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 deadlock-mod-manager/deadlock-mod-manager --skill git-conventions -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install deadlock-mod-manager/deadlock-mod-manager git-conventions --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deadlock-mod-manager/deadlock-mod-manager.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/git-conventions .cursor/skills/git-conventions && 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 "git-conventions" agent skill from https://github.com/deadlock-mod-manager/deadlock-mod-manager/tree/main/.agents/skills/git-conventions into .cursor/skills/git-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-conventions", 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/deadlock-mod-manager/deadlock-mod-manager.git --path .agents/skills/git-conventions--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 deadlock-mod-manager/deadlock-mod-manager --skill git-conventions -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install deadlock-mod-manager/deadlock-mod-manager git-conventions --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deadlock-mod-manager/deadlock-mod-manager.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/git-conventions .gemini/skills/git-conventions && 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 "git-conventions" agent skill from https://github.com/deadlock-mod-manager/deadlock-mod-manager/tree/main/.agents/skills/git-conventions into .gemini/skills/git-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-conventions", 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 deadlock-mod-manager/deadlock-mod-manager git-conventionsInstalls 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 deadlock-mod-manager/deadlock-mod-manager --skill git-conventions -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/deadlock-mod-manager/deadlock-mod-manager.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/git-conventions .github/skills/git-conventions && 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 "git-conventions" agent skill from https://github.com/deadlock-mod-manager/deadlock-mod-manager/tree/main/.agents/skills/git-conventions into .github/skills/git-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-conventions", 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 deadlock-mod-manager/deadlock-mod-manager --skill git-conventions -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install deadlock-mod-manager/deadlock-mod-manager git-conventions --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deadlock-mod-manager/deadlock-mod-manager.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/git-conventions .opencode/skills/git-conventions && 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 "git-conventions" agent skill from https://github.com/deadlock-mod-manager/deadlock-mod-manager/tree/main/.agents/skills/git-conventions into .opencode/skills/git-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-conventions", 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
git-conventions- GitHub stars
- 574
- Token cost
- ~1.4k tokens
- SKILL.md length
- 476 words
- Files
- 1
- Skills in repo
- 25
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Git Conventions: Guidelines for commit messages, branch naming, and version control practices
- Tasks that involve Git workflow
- SKILL.md covers Commit Message Format, Examples, Branch Naming Conventions and Gathering Git Context, plus 1 more section
- Calls git
- Tasks that involve Commit messages
What it does
Git Conventions is an agent skill from deadlock-mod-manager/deadlock-mod-manager. Git Conventions: Guidelines for commit messages, branch naming, and version control practices
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Git workflow and Commit messages. It works with Git. The repository describes itself as: A mod manager for the Valve game Deadlock. The licence is GPL-3.0.
When your agent uses it
- Tasks that involve Git workflow
- Tasks that involve Commit messages
Example prompts
- “/git-conventions”
What it can do on your machine
Read from SKILL.md and the folder at commit 45c273c. 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.orgsemver.orgkeepachangelog.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
Git Conventions loads about 1.4k tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 476 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
The full file from deadlock-mod-manager/deadlock-mod-manager at commit 45c273c, republished under its GPL-3.0 licence (© deadlock-mod-manager). 476 words, ~1,392 tokens.
Download SKILL.mdSave it as
.claude/skills/git-conventions/SKILL.md (or your agent's skills folder).- name
- git-conventions
- description
- Git Conventions: Guidelines for commit messages, branch naming, and version control practices
Git Commit and Version Control Conventions
Commit Message Format
This project follows the Conventional Commits specification for commit messages. This format enables automatic changelog generation, version bumping, and better collaboration.
Structure
<type>(<scope>): <subject>
[optional body]
[optional footer(s)]Type
The type must be one of the following:
feat- A new feature for the userfix- A bug fixdocs- Documentation only changesstyle- Changes that don't affect the meaning of code (white-space, formatting, etc.)refactor- Code change that neither fixes a bug nor adds a featureperf- Code change that improves performancetest- Adding missing tests or correcting existing testsbuild- Changes that affect the build system or external dependenciesci- Changes to CI configuration files and scriptschore- Other changes that don't modify src or test filesrevert- Reverts a previous commit
Scope
The scope should be the name of the package or area affected. For this monorepo:
Apps:
api- Backend API servicebot- Discord botdesktop- Desktop applicationlockdex- Lockdex servicewww- Web applicationmirror-service- Mirror service
Packages:
common- Common utilitiesdatabase- Database schema and clientlogging- Logging packageshared- Shared utilitiesvpk-parser- VPK parser
Other:
deps- Dependency updatesrepo- Repository-wide changesrelease- Release-related changes
Subject
The subject contains a succinct description of the change:
- Use the imperative, present tense: "change" not "changed" nor "changes"
- Don't capitalize the first letter
- No period (.) at the end
- Keep it under 72 characters
Body (Optional)
The body should include the motivation for the change and contrast this with previous behavior.
- Use the imperative, present tense
- Wrap at 72 characters
- Separate from subject with a blank line
Footer (Optional)
The footer should contain information about Breaking Changes and reference issues that this commit closes.
Breaking Changes should start with BREAKING CHANGE: followed by a description.
Closes references should be on a separate line and use the format: Closes #123, #456
Show full SKILL.md (175 more words)Show less
Examples
Feature Addition
feat(desktop): add mod conflict detection
Implement visual indicators for mod conflicts and add conflict
resolution suggestions to the UI.
Closes #142Bug Fix
fix(api): handle edge case in pagination
Fix incorrect offset calculation when page size exceeds total items.
This prevents API errors when requesting pages beyond available data.Breaking Change
feat(api)!: remove deprecated v1 endpoints
BREAKING CHANGE: The /v1/mods endpoint has been removed. All clients
must migrate to the /v2/mods endpoint which provides better filtering
and pagination support.
Migration guide available at docs/migration/v1-to-v2.mdDependency Update
chore(deps): update @tauri-apps/api to v2.1.0Documentation
docs(readme): add installation instructions for LinuxMultiple Scopes
refactor(desktop,shared): extract mod validation logic to shared packageSimple Fix
fix(www): correct button alignment on mobileBranch Naming Conventions
Branch Format
<type>/<ticket-or-description>Types
feature/- New featuresbugfix/- Bug fixeshotfix/- Critical fixes that need immediate deploymentrefactor/- Code refactoringchore/- Maintenance tasksdocs/- Documentation updates
Branch Naming Rules
- Use kebab-case for descriptions
- Include ticket/issue numbers when applicable
- Keep names descriptive but concise
- Use lowercase letters
Branch Examples
# With ticket number
feature/KR-123-add-mod-collections
bugfix/KR-456-fix-download-crash
hotfix/KR-789-security-patch
# Without ticket number
feature/dark-mode-toggle
bugfix/pagination-edge-case
refactor/extract-validation-logic
chore/update-dependencies
docs/add-api-examplesGathering Git Context
Run this single command to gather all necessary information:
echo "=== BRANCH ===" && git rev-parse --abbrev-ref HEAD && echo "=== STAGED FILES ===" && git diff --staged --stat && echo "=== STAGED CHANGES ===" && git diff --stagedThis provides:
- Current branch name
- Staged files summary → determine scope (which workspace/package)
- Actual changes → determine commit type and write description
Changesets Integration
This project uses changesets for version management. See 090-changesets.mdc for details on when and how to create changesets alongside commits.
Current branch (agents)
When running /commit or creating commits for the user, use the checked-out
branch as-is. Do not create, switch to, or require a feature branch only
because the current branch is main or master, unless the user explicitly
asks for a different branch.
References
- Conventional Commits Specification
- Semantic Versioning
- Keep a Changelog
- Project Changeset Guidelines
© deadlock-mod-manager, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/git-conventions of deadlock-mod-manager/deadlock-mod-manager.
Open the folder on GitHubat commit 45c273c
Compare with similar skills
Git Conventions 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 |
|---|---|---|---|---|---|---|
| Git Conventions this skilldeadlock-mod-manager/deadlock-mod-manager | 574 | — | ~1.4k | Automated safety check: Pass | GPL-3.0 | |
| 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 | |
| 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 deadlock-mod-manager/deadlock-mod-manager
All 25 skills in this repoSkill Creator
deadlock-mod-manager/deadlock-mod-manager
Create new agent skills following the Agent Skills specification.
Create Auth Skill
deadlock-mod-manager/deadlock-mod-manager
Scaffold and implement authentication in TypeScript/JavaScript apps using Better Auth.
Opensrc
deadlock-mod-manager/deadlock-mod-manager
Fetch source code for npm, PyPI, or crates.io packages and GitHub/GitLab repos to provide AI agents with implementation context beyond types and docs.
Security Review
deadlock-mod-manager/deadlock-mod-manager
Security code review for Tauri/Rust/TypeScript desktop apps and Hono/oRPC APIs.
Babysit
deadlock-mod-manager/deadlock-mod-manager
Stay on one pull request until it is merge-ready, fixing the highest-priority blocker and telling the user when it is green.
Changeset
deadlock-mod-manager/deadlock-mod-manager
Generate a changeset file describing the current PR's changes.
Related
Works with
Categories
Questions about Git Conventions
What does Git Conventions do?
Git Conventions: Guidelines for commit messages, branch naming, and version control practices. Git Conventions is an agent skill from deadlock-mod-manager/deadlock-mod-manager.
When should I use Git Conventions?
Git Conventions fits situations like: tasks that involve Git workflow; tasks that involve Commit messages.
How do I install Git Conventions in Claude Code?
Run `npx skills add deadlock-mod-manager/deadlock-mod-manager --skill git-conventions -a claude-code`. Or copy the skill folder (.agents/skills/git-conventions in deadlock-mod-manager/deadlock-mod-manager) into .claude/skills/git-conventions in your project. Claude Code loads it when a task matches its description.
How do I install Git Conventions in Codex?
Run `npx skills add deadlock-mod-manager/deadlock-mod-manager --skill git-conventions -a codex`. Or copy the skill folder (.agents/skills/git-conventions in deadlock-mod-manager/deadlock-mod-manager) into .agents/skills/git-conventions in your project. Codex loads it when a task matches its description.
Can I use Git Conventions 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 deadlock-mod-manager/deadlock-mod-manager --skill git-conventions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/git-conventions, .gemini/skills/git-conventions, .github/skills/git-conventions and .opencode/skills/git-conventions in your project.
What does Git Conventions need to run?
Going by SKILL.md and its folder, Git Conventions needs the command-line tools its instructions call (git).
Does Git Conventions access the network?
SKILL.md names 3 domains. As links in the text: conventionalcommits.org, semver.org and keepachangelog.com. This is read from the text; nothing was executed.
Is Git Conventions 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 Git Conventions use?
Git Conventions is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Git Conventions use?
About 1.4k tokens (SKILL.md is roughly 5.6k 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 Git Conventions?
Skills that share tags, products or a category with Git Conventions: ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 103k 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 Git Conventions?
deadlock-mod-manager (a GitHub organization) maintains it in deadlock-mod-manager/deadlock-mod-manager, which has 574 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 8, 2026.
Source: deadlock-mod-manager/deadlock-mod-manager on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.