Generate Release Notes
teambit/bit
Generate comprehensive release notes for Bit from git commits and pull requests.
Write a commit message for the current changes - conventional commit format, a short body, issue references in the footer.
Install Conventional Commit
$ npx skills add jetstreamapp/jetstream --skill conventional-commit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jetstreamapp/jetstream conventional-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/jetstreamapp/jetstream.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/conventional-commit .claude/skills/conventional-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 "conventional-commit" agent skill from https://github.com/jetstreamapp/jetstream/tree/main/.claude/skills/conventional-commit into .claude/skills/conventional-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-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/jetstreamapp/jetstream/tree/main/.claude/skills/conventional-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 jetstreamapp/jetstream --skill conventional-commit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jetstreamapp/jetstream conventional-commit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jetstreamapp/jetstream.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/conventional-commit .agents/skills/conventional-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 "conventional-commit" agent skill from https://github.com/jetstreamapp/jetstream/tree/main/.claude/skills/conventional-commit into .agents/skills/conventional-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-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 jetstreamapp/jetstream --skill conventional-commit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jetstreamapp/jetstream conventional-commit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jetstreamapp/jetstream.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/conventional-commit .cursor/skills/conventional-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 "conventional-commit" agent skill from https://github.com/jetstreamapp/jetstream/tree/main/.claude/skills/conventional-commit into .cursor/skills/conventional-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-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/jetstreamapp/jetstream.git --path .claude/skills/conventional-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 jetstreamapp/jetstream --skill conventional-commit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jetstreamapp/jetstream conventional-commit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jetstreamapp/jetstream.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/conventional-commit .gemini/skills/conventional-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 "conventional-commit" agent skill from https://github.com/jetstreamapp/jetstream/tree/main/.claude/skills/conventional-commit into .gemini/skills/conventional-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-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 jetstreamapp/jetstream conventional-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 jetstreamapp/jetstream --skill conventional-commit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jetstreamapp/jetstream.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/conventional-commit .github/skills/conventional-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 "conventional-commit" agent skill from https://github.com/jetstreamapp/jetstream/tree/main/.claude/skills/conventional-commit into .github/skills/conventional-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-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 jetstreamapp/jetstream --skill conventional-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 jetstreamapp/jetstream conventional-commit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jetstreamapp/jetstream.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/conventional-commit .opencode/skills/conventional-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 "conventional-commit" agent skill from https://github.com/jetstreamapp/jetstream/tree/main/.claude/skills/conventional-commit into .opencode/skills/conventional-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conventional-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
conventional-commit- GitHub stars
- 125
- Token cost
- ~1.3k tokens
- SKILL.md length
- 606 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Write a commit message for the current changes - conventional commit format, a short body, issue references in the footer.
- Works in 5 steps: Read the whole change first: git status,… → git log --oneline -10 to match current… → Stage what belongs in this commit. → …
- Shorten a commit message
- SKILL.md covers Shape, Length, Subject and Body, plus 3 more sections
- Calls git
What it does
Conventional Commit is an agent skill from jetstreamapp/jetstream. Write a commit message for the current changes - conventional commit format, a short body, issue references in the footer. Use whenever asked to write, draft, revise, or shorten a commit message, or to commit staged work. Also applies to PR descriptions, since the commit message doubles as one.
Its SKILL.md is about 1.3k 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 Commit messages. It works with Salesforce, React, TypeScript and Node.js. The repository describes itself as: A better way to build on Salesforce.
When your agent uses it
- Shorten a commit message
- Commit staged work
Example prompts
- “/conventional-commit”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Read the whole change first: git status, then git diff (or
- git log --oneline -10 to match current subject conventions.
- Stage what belongs in this commit.
- Draft, then cut. Of every body line ask: does this still earn its place in a
- Commit with a heredoc so the wrapping survives. Commitlint runs on the hook -
What it can do on your machine
Read from SKILL.md and the folder at commit cf959cd. 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
Conventional Commit loads about 1.3k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 606 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 606 words (~1,333 tokens).
“Commitlint runs on every commit via .husky/commit-msg, and the header feeds the generated CHANGELOG.md, so the header is public and permanent. The body is for the next developer who runs git blame on a line that looks wrong - not…”
- name
- conventional-commit
Files
Just SKILL.md in .claude/skills/conventional-commit of jetstreamapp/jetstream.
Open the folder on GitHubat commit cf959cd
Compare with similar skills
Conventional 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Conventional Commit this skilljetstreamapp/jetstream | 125 | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Generate Release Notesteambit/bit | 18k | — | ~2.2k | Automated safety check: Pass | Custom licence | |
| Coding Standardskurealnum/dotfiles | 290 | 17 repos | ~2.9k | Automated safety check: Pass | None | |
| Bit CLIteambit/bit | 18k | — | ~2k | Automated safety check: Warn | Custom licence | |
| CommitMagic-Resume/Magic-Resume | 101 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Coding Standardsaffaan-m/ECC | 274k | 3 repos | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
Coding Standards
kurealnum/dotfiles
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
Bit CLI
teambit/bit
MUST consult before running ANY bit command. An agent skill from teambit/bit.
Commit
Magic-Resume/Magic-Resume
Write a Magic Resume commit message that passes the gitmoji + conventional-type lint.
Coding Standards
affaan-m/ECC
适用于TypeScript、JavaScript、React和Node.js开发的通用编码标准、最佳实践和模式. An agent skill from affaan-m/ECC.
Coding Standards
affaan-m/ECC
TypeScript、JavaScript、React、Node.js開発のための汎用コーディング標準、ベストプラクティス、パターン。
More from jetstreamapp/jetstream
Gh Bot Comment
jetstreamapp/jetstream
Post GitHub PR/issue comments, reviews, and review replies as the Jetstream bot account instead of the user's personal account.
Related
Works with
Categories
Questions about Conventional Commit
What does Conventional Commit do?
Write a commit message for the current changes - conventional commit format, a short body, issue references in the footer. Conventional Commit is an agent skill from jetstreamapp/jetstream. Write a commit message for the current changes - conventional commit format, a short body, issue references in the footer.
When should I use Conventional Commit?
Conventional Commit fits situations like: shorten a commit message; commit staged work.
How do I install Conventional Commit in Claude Code?
Run `npx skills add jetstreamapp/jetstream --skill conventional-commit -a claude-code`. Or copy the skill folder (.claude/skills/conventional-commit in jetstreamapp/jetstream) into .claude/skills/conventional-commit in your project. Claude Code loads it when a task matches its description.
How do I install Conventional Commit in Codex?
Run `npx skills add jetstreamapp/jetstream --skill conventional-commit -a codex`. Or copy the skill folder (.claude/skills/conventional-commit in jetstreamapp/jetstream) into .agents/skills/conventional-commit in your project. Codex loads it when a task matches its description.
Can I use Conventional 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 jetstreamapp/jetstream --skill conventional-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/conventional-commit, .gemini/skills/conventional-commit, .github/skills/conventional-commit and .opencode/skills/conventional-commit in your project.
What does Conventional Commit need to run?
Going by SKILL.md and its folder, Conventional Commit needs the command-line tools its instructions call (git).
Does Conventional 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 Conventional 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 Conventional Commit use?
Conventional Commit 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 Conventional 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 Conventional Commit?
Skills that share tags, products or a category with Conventional Commit: Generate Release Notes (teambit/bit, 18k stars), Coding Standards (kurealnum/dotfiles, 290 stars), Bit CLI (teambit/bit, 18k stars) and Commit (Magic-Resume/Magic-Resume, 101 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Conventional Commit?
jetstreamapp (a GitHub organization) maintains it in jetstreamapp/jetstream, which has 125 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 6, 2026.
Source: jetstreamapp/jetstream on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.