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.
Guides the agent through making a focused git commit in the Ghost repository: inspect state, stage only relevant files, follow the contributing rules, then verify.
Install Ghost Commit Workflow
$ npx skills add TryGhost/Ghost --skill commit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install TryGhost/Ghost 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/TryGhost/Ghost.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/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/TryGhost/Ghost/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 install https://github.com/TryGhost/Ghost/tree/main/.agents/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 TryGhost/Ghost --skill commit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install TryGhost/Ghost commit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TryGhost/Ghost.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/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/TryGhost/Ghost/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.
$ npx skills add TryGhost/Ghost --skill commit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install TryGhost/Ghost commit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TryGhost/Ghost.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/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/TryGhost/Ghost/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 https://github.com/TryGhost/Ghost.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.
$ npx skills add TryGhost/Ghost --skill commit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install TryGhost/Ghost commit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TryGhost/Ghost.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/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/TryGhost/Ghost/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.
$ gh skill install TryGhost/Ghost 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 TryGhost/Ghost --skill commit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/TryGhost/Ghost.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/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/TryGhost/Ghost/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.
$ npx skills add TryGhost/Ghost --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 TryGhost/Ghost commit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TryGhost/Ghost.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/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/TryGhost/Ghost/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
- 55k
- Token cost
- ~286 tokens
- SKILL.md length
- 157 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
Guides the agent through making a focused git commit in the Ghost repository: inspect state, stage only relevant files, follow the contributing rules, then verify.
- Works in 5 steps: Review the current git state before… → Only stage files relevant to the… → Read and follow… → …
- Committing finished work in the Ghost repository
- SKILL.md covers Instructions and Important
- Calls git
What it does
The skill applies whenever you ask for a commit of the current work. The agent reviews `git status`, `git diff` and the recent log, stages only files that belong to the change, and leaves out unrelated untracked files, generated files and local artifacts. Message conventions are not restated; the agent reads and follows the commit message section of `.github/CONTRIBUTING.md`, which is the source of truth for the project.
For publishable packages it checks whether a release intent is needed: a package `README.md` is published and needs one, while repository-only Markdown such as `AGENTS.md`, changelogs and package-local `docs/` does not. After committing it runs `git status --short` to confirm the result. It does not push unless asked, avoids empty commits, keeps commits focused, and fixes a failing hook with a new commit and never bypasses it.
When your agent uses it
- Committing finished work in the Ghost repository
- Splitting unrelated changes into separate focused commits
- Checking whether a package change needs a release intent
Example prompts
- “Commit my changes to the members settings screen.”
- “Stage only the files for the newsletter fix and commit them, leaving the rest alone.”
- “Does my README change in the admin package need a release intent before I commit?”
Requirements
- Git in a checkout of the Ghost repository
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Review the current git state before committing
- Only stage files relevant to the requested change. Do not include unrelated untracked files, generated files, or likely-local artifacts.
- Read and follow .github/CONTRIBUTING.md#commit-messages. It is the
- For publishable packages, check whether a release intent is required. A
- Run git status --short after committing and confirm the result.
What it can do on your machine
Read from SKILL.md and the folder at commit 7aecaf7. 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
Ghost Commit Workflow loads about 286 tokens when it runs. Until then it costs about 12 tokens; SKILL.md has 157 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 TryGhost/Ghost at commit 7aecaf7, republished under its MIT licence (© TryGhost). 157 words, ~286 tokens.
Download SKILL.mdSave it as
.claude/skills/commit/SKILL.md (or your agent's skills folder).- name
- commit
- description
- Commit message formatting and guidelines
Commit
Use this skill whenever the user asks you to create a git commit for the current work.
Instructions
- Review the current git state before committing:
git statusgit diffgit log -5 --oneline
- Only stage files relevant to the requested change. Do not include unrelated untracked files, generated files, or likely-local artifacts.
- Read and follow
.github/CONTRIBUTING.md#commit-messages. It is the source of truth for Ghost's commit conventions. - For publishable packages, check whether a release intent is required. A
package
README.mdis published and requires a release; repository-only Markdown such asAGENTS.md, changelogs, and package-localdocs/does not. - Run
git status --shortafter committing and confirm the result.
Important
- Do not push to remote unless the user explicitly asks
- Keep commits focused and avoid bundling unrelated changes
- If there are no relevant changes, do not create an empty commit
- If hooks fail, fix the issue and create a new commit. Never bypass hooks.
© TryGhost, MIT. 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/commit of TryGhost/Ghost.
Open the folder on GitHubat commit 7aecaf7
Compare with similar skills
Ghost Commit Workflow 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 |
|---|---|---|---|---|---|---|
| Ghost Commit Workflow this skillTryGhost/Ghost | 55k | — | ~286 | 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 | 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 TryGhost/Ghost
Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
Convert Internal Package to TypeScript
TryGhost/Ghost
Moves a legacy internal Ghost package from JavaScript and CommonJS to TypeScript and ESM in three focused commits that keep git file history intact.
Ghost Private Feature Flag
TryGhost/Ghost
Adds a private developer-experiments feature flag to Ghost, covering the backend registration, the Labs settings toggle and the test snapshot updates.
Tinybird CLI Guidelines
TryGhost/Ghost
Guidance for running the Tinybird tb CLI: choosing local, branch or cloud workflows, building and deploying, loading data, handling tokens and secrets, and CI/CD.
Tinybird Datafile Rules
TryGhost/Ghost
Rules for writing Tinybird datasources, pipes, endpoints and materialized views, with SQL constraints, optimization habits and deduplication patterns.
Admin7 Feature Flags
TryGhost/Ghost
Add, consume, review, or remove Admin 7 milestone flags using Ghost's existing Labs conventions.
Related
Works with
Categories
Questions about Ghost Commit Workflow
What does Ghost Commit Workflow do?
Guides the agent through making a focused git commit in the Ghost repository: inspect state, stage only relevant files, follow the contributing rules, then verify. The skill applies whenever you ask for a commit of the current work. The agent reviews `git status`, `git diff` and the recent log, stages only files that belong to the change, and leaves out unrelated untracked files, generated files and local artifacts.
When should I use Ghost Commit Workflow?
Ghost Commit Workflow fits situations like: committing finished work in the Ghost repository; splitting unrelated changes into separate focused commits; checking whether a package change needs a release intent.
How do I install Ghost Commit Workflow in Claude Code?
Run `npx skills add TryGhost/Ghost --skill commit -a claude-code`. Or copy the skill folder (.agents/skills/commit in TryGhost/Ghost) into .claude/skills/commit in your project. Claude Code loads it when a task matches its description.
How do I install Ghost Commit Workflow in Codex?
Run `npx skills add TryGhost/Ghost --skill commit -a codex`. Or copy the skill folder (.agents/skills/commit in TryGhost/Ghost) into .agents/skills/commit in your project. Codex loads it when a task matches its description.
Can I use Ghost Commit Workflow 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 TryGhost/Ghost --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 Ghost Commit Workflow need to run?
Going by SKILL.md and its folder, Ghost Commit Workflow needs the command-line tools its instructions call (git). Our summary lists: Git in a checkout of the Ghost repository.
Does Ghost Commit Workflow 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 Ghost Commit Workflow 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 Ghost Commit Workflow use?
Ghost Commit Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ghost Commit Workflow use?
About 286 tokens (SKILL.md is roughly 1.1k 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 Ghost Commit Workflow?
Skills that share tags, products or a category with Ghost Commit Workflow: 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 Ghost Commit Workflow?
TryGhost (a GitHub organization) maintains it in TryGhost/Ghost, which has 55,493 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.
Source: TryGhost/Ghost on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.