Conventional Commit
jetstreamapp/jetstream
Write a commit message for the current changes - conventional commit format, a short body, issue references in the footer.
Conventional Commits 1.0.0 specification for SWPM. An agent skill from deinsoftware/swpm.
Install Swpm Conventional Commits
$ npx skills add deinsoftware/swpm --skill swpm-conventional-commits -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install deinsoftware/swpm swpm-conventional-commits --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/deinsoftware/swpm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/swpm-conventional-commits .claude/skills/swpm-conventional-commits && 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 "swpm-conventional-commits" agent skill from https://github.com/deinsoftware/swpm/tree/main/.agents/skills/swpm-conventional-commits into .claude/skills/swpm-conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swpm-conventional-commits", 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/deinsoftware/swpm/tree/main/.agents/skills/swpm-conventional-commitsType 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 deinsoftware/swpm --skill swpm-conventional-commits -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install deinsoftware/swpm swpm-conventional-commits --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deinsoftware/swpm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/swpm-conventional-commits .agents/skills/swpm-conventional-commits && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "swpm-conventional-commits" agent skill from https://github.com/deinsoftware/swpm/tree/main/.agents/skills/swpm-conventional-commits into .agents/skills/swpm-conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swpm-conventional-commits", 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 deinsoftware/swpm --skill swpm-conventional-commits -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install deinsoftware/swpm swpm-conventional-commits --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deinsoftware/swpm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/swpm-conventional-commits .cursor/skills/swpm-conventional-commits && 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 "swpm-conventional-commits" agent skill from https://github.com/deinsoftware/swpm/tree/main/.agents/skills/swpm-conventional-commits into .cursor/skills/swpm-conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swpm-conventional-commits", 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/deinsoftware/swpm.git --path .agents/skills/swpm-conventional-commits--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 deinsoftware/swpm --skill swpm-conventional-commits -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install deinsoftware/swpm swpm-conventional-commits --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deinsoftware/swpm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/swpm-conventional-commits .gemini/skills/swpm-conventional-commits && 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 "swpm-conventional-commits" agent skill from https://github.com/deinsoftware/swpm/tree/main/.agents/skills/swpm-conventional-commits into .gemini/skills/swpm-conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swpm-conventional-commits", 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 deinsoftware/swpm swpm-conventional-commitsInstalls 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 deinsoftware/swpm --skill swpm-conventional-commits -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/deinsoftware/swpm.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/swpm-conventional-commits .github/skills/swpm-conventional-commits && 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 "swpm-conventional-commits" agent skill from https://github.com/deinsoftware/swpm/tree/main/.agents/skills/swpm-conventional-commits into .github/skills/swpm-conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swpm-conventional-commits", 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 deinsoftware/swpm --skill swpm-conventional-commits -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install deinsoftware/swpm swpm-conventional-commits --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deinsoftware/swpm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/swpm-conventional-commits .opencode/skills/swpm-conventional-commits && 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 "swpm-conventional-commits" agent skill from https://github.com/deinsoftware/swpm/tree/main/.agents/skills/swpm-conventional-commits into .opencode/skills/swpm-conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "swpm-conventional-commits", 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
swpm-conventional-commits- GitHub stars
- 125
- Token cost
- ~1.6k tokens
- SKILL.md length
- 559 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
Conventional Commits 1.0.0 specification for SWPM. An agent skill from deinsoftware/swpm.
- Works in 7 steps: Determine the correct type (feat, fix,… → Add scope if applicable: feat(parser) → Write imperative description after → …
- Tasks that involve Commit messages
- SKILL.md covers When to Use, Conventional Commits 1.0.0 Rules, SWPM Commit Conventions and Mapping to SemVer, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Swpm Conventional Commits is an agent skill from deinsoftware/swpm. Conventional Commits 1.0.0 specification for SWPM. Defines commit message format with types (feat, fix, etc.), scopes, breaking changes, and body/footer conventions. Activates when writing commit messages or modifying git commits.
Its SKILL.md is about 1.6k 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 Node.js. The repository describes itself as: Switch Package Manager - Say goodbye to Package Manager confusion. The licence is MIT.
When your agent uses it
- Tasks that involve Commit messages
Example prompts
- “/swpm-conventional-commits”
Requirements
- Node.js
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Determine the correct type (feat, fix, etc.)
- Add scope if applicable: feat(parser)
- Write imperative description after
- Add ! or BREAKING CHANGE: footer for breaking changes
- Add body with blank line separation if needed
- Add footers (Reviewed-by, Refs, etc.) if needed
- Ensure description uses imperative mood
What it can do on your machine
Read from SKILL.md and the folder at commit ee443bd. 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
No scripts in the folder and no shell commands in SKILL.md.
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.org
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
Swpm Conventional Commits loads about 1.6k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 559 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 deinsoftware/swpm at commit ee443bd, republished under its MIT licence (© deinsoftware). 559 words, ~1,553 tokens.
Download SKILL.mdSave it as
.claude/skills/swpm-conventional-commits/SKILL.md (or your agent's skills folder).- name
- swpm-conventional-commits
- description
- Conventional Commits 1.0.0 specification for SWPM. Defines commit message format with types (feat, fix, etc.), scopes, breaking changes, and body/footer conventions. Activates when writing commit messages or modifying git commits.
- id
- swpm-conventional-commits
- version
- 1.0.0
- tags
- swpm, conventional-commits, git, commit-messages
SWPM Conventional Commits Standards
Use this skill when writing commit messages, questions about commit format, or when modifying git commits for SWPM.
When to Use
- User is writing a commit message - activates to ensure Conventional Commits 1.0.0 format
- Developer asks "What type should this commit be?"
- Questions about commit message structure
- Adding breaking changes to commits
- Do not use for CHANGELOG formatting (use
swpm-keepachangelog) or version numbering (useswpm-semver)
Conventional Commits 1.0.0 Rules
Commit Message Structure
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]Types
Required type prefix:
- feat: A new feature (correlates with MINOR in SemVer)
- fix: A bug fix (correlates with PATCH in SemVer)
- BREAKING CHANGE: Introduces breaking API change (correlates with MAJOR in SemVer)
Additional Types (not mandated by spec, but allowed)
- build: Changes that affect build system or external dependencies
- chore: Other changes that don't modify src or test files
- ci: Changes to CI configuration files and scripts
- docs: Documentation only changes
- perf: A code change that improves performance
- refactor: A code change that neither fixes a bug nor adds a feature
- style: Changes that do not affect the meaning of the code (white-space, formatting)
- test: Adding missing tests or correcting existing tests
Scope (Optional)
feat(parser): add ability to parse arrays
fix(api): resolve null pointer exceptionScope MUST be a noun describing a section of the codebase surrounded by parentheses.
Breaking Changes
Option 1: Using ! after type/scope
feat!: send an email to the customer when a product is shipped
feat(api)!: send an email to the customer when a product is shippedOption 2: Using BREAKING CHANGE footer
feat: allow provided config object to extend other configs
BREAKING CHANGE: `extends` key in config file is now used for extending other config filesDescription
- MUST immediately follow the colon and space after type/scope
- Short summary of the code changes
- Use imperative mood: "add" not "added" or "adds"
Body (Optional)
- MUST begin one blank line after the description
- Free-form and MAY consist of any number of newline separated paragraphs
- Provide additional contextual information
Footers (Optional)
- MUST begin one blank line after the body
- Each footer MUST consist of a word token, followed by either
:or# - Token MUST use
-instead of whitespace (e.g.,Reviewed-by) - Exception:
BREAKING CHANGEMAY be uppercase
SWPM Commit Conventions
Commit Message Examples
✅ Correct - Simple fix
fix: resolve volta version detection when not installed✅ Correct - New feature with scope
feat(commands): add support for bun package manager✅ Correct - Breaking change with !
feat!: remove deprecated `why` command
BREAKING CHANGE: The `why` command has been removed. Use `pnpm why` directly.✅ Correct - With body and footers
fix: prevent racing of requests
Introduce a request id and a reference to latest request. Dismiss
incoming responses other than from latest request.
Reviewed-by: equiman
Refs: #123✅ Correct - Build/CI changes
build: upgrade dependencies to latest versions
chore: update package.json scripts
ci: add Node.js 20 to build matrix
docs: update README with new command examples
test: add unit tests for args translator
refactor: simplify command translation logic❌ Incorrect
fixed bug // Wrong type, not imperative
add new feature // Missing type prefix
Feat: new command // Wrong case (should be lowercase)
feat: add feature
extra line // Extra blank line in wrong placeShow full SKILL.md (229 more words)Show less
Mapping to SemVer
Conventional Commits maps to Semantic Versioning:
- fix → PATCH (e.g.,
2.6.0→2.6.1) - feat → MINOR (e.g.,
2.6.0→2.7.0) - BREAKING CHANGE → MAJOR (e.g.,
2.6.0→3.0.0)
Commit Checklist
Before committing:
- Determine the correct type (feat, fix, etc.)
- Add scope if applicable:
feat(parser): - Write imperative description after
: - Add
!orBREAKING CHANGE:footer for breaking changes - Add body with blank line separation if needed
- Add footers (Reviewed-by, Refs, etc.) if needed
- Ensure description uses imperative mood
Example Questions
Q: "What type should I use for updating dependencies?"
A: Use build: or chore::
build: upgrade dependencies to latest versionsQ: "How do I indicate a breaking change?"
A: Use ! after type or add BREAKING CHANGE: footer:
feat!: remove deprecated command
BREAKING CHANGE: Command removed in this version.Q: "What's the difference between feat and fix?"
A: feat adds new functionality (→ MINOR version), fix patches bugs (→ PATCH version).
Q: "Can I use multiple types in one commit?" A: No, each commit should have one type. Make separate commits for different changes.
Q: "Should I use uppercase FEAT or lowercase feat?"
A: Use lowercase feat:, but BREAKING CHANGE: footer MUST be uppercase.
Observations
Before helping with commit messages:
- Check if the change is a new feature (feat), bug fix (fix), or breaking change (BREAKING CHANGE)
- Determine if a scope applies (e.g.,
commands,args,docs) - Verify description uses imperative mood ("add" not "added")
- Check if commit includes body/footers
- Reference: https://www.conventionalcommits.org/en/v1.0.0/
Reference
Full Conventional Commits specification: https://www.conventionalcommits.org/en/v1.0.0/
© deinsoftware, 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/swpm-conventional-commits of deinsoftware/swpm.
Open the folder on GitHubat commit ee443bd
Compare with similar skills
Swpm Conventional Commits 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 |
|---|---|---|---|---|---|---|
| Swpm Conventional Commits this skilldeinsoftware/swpm | 125 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Conventional Commitjetstreamapp/jetstream | 126 | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Git Commit Convention7-e1even/learn-agent | 284 | — | ~206 | Automated safety check: Pass | MIT | |
| Electron Multi-Process ArchitectureiOfficeAI/AionUi | 33k | 1 repos | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Contextual Commit Messagesyamadashy/repomix | 29k | 1 repos | ~2.7k | Automated safety check: Pass | MIT | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Git Commit Convention
7-e1even/learn-agent
写 git 提交信息、整理提交历史时使用——Conventional Commits 的格式、类型选择和拆分原则. An agent skill from 7-e1even/learn-agent.
Electron Multi-Process Architecture
iOfficeAI/AionUi
Tells the agent where new code belongs in an Electron multi-process project and which APIs each process may use, with rules for new bridges, services, agents and workers.
Contextual Commit Messages
yamadashy/repomix
Writes Conventional Commits whose bodies carry action lines recording the intent, decisions and constraints behind a change, not only what changed.
React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
Caveman Commit
vishiri/fantasia-archive
Ultra-compressed commit message generator. An agent skill from vishiri/fantasia-archive.
More from deinsoftware/swpm
Swpm Code Review
deinsoftware/swpm
Automated code review bash script for SWPM. An agent skill from deinsoftware/swpm.
Swpm Keepachangelog
deinsoftware/swpm
Keep a Changelog 1.1.0 standards for SWPM. An agent skill from deinsoftware/swpm.
Swpm Release
deinsoftware/swpm
Automated release bash script for SWPM. An agent skill from deinsoftware/swpm.
Swpm Semver
deinsoftware/swpm
Semantic Versioning 2.0.0 guidelines for SWPM. An agent skill from deinsoftware/swpm.
Swpm Dev Guide
deinsoftware/swpm
Development guide for setting up, debugging, and testing SWPM locally.
Swpm Manage Commands Args
deinsoftware/swpm
Manage cmds and args props in SWPM package manager configs (src/packages/managers/.ts), including adding, modifying or removing command and argument mappings across npm, yarn, pnpm, bun, deno.
Related
Works with
Categories
Questions about Swpm Conventional Commits
What does Swpm Conventional Commits do?
Conventional Commits 1.0.0 specification for SWPM. An agent skill from deinsoftware/swpm. Swpm Conventional Commits is an agent skill from deinsoftware/swpm.0 specification for SWPM.
When should I use Swpm Conventional Commits?
Swpm Conventional Commits fits situations like: tasks that involve Commit messages.
How do I install Swpm Conventional Commits in Claude Code?
Run `npx skills add deinsoftware/swpm --skill swpm-conventional-commits -a claude-code`. Or copy the skill folder (.agents/skills/swpm-conventional-commits in deinsoftware/swpm) into .claude/skills/swpm-conventional-commits in your project. Claude Code loads it when a task matches its description.
How do I install Swpm Conventional Commits in Codex?
Run `npx skills add deinsoftware/swpm --skill swpm-conventional-commits -a codex`. Or copy the skill folder (.agents/skills/swpm-conventional-commits in deinsoftware/swpm) into .agents/skills/swpm-conventional-commits in your project. Codex loads it when a task matches its description.
Can I use Swpm Conventional Commits 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 deinsoftware/swpm --skill swpm-conventional-commits -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/swpm-conventional-commits, .gemini/skills/swpm-conventional-commits, .github/skills/swpm-conventional-commits and .opencode/skills/swpm-conventional-commits in your project.
What does Swpm Conventional Commits need to run?
SKILL.md names no scripts, command-line tools or credentials: Swpm Conventional Commits is instructions for the agent only. Our summary lists: Node.js.
Does Swpm Conventional Commits access the network?
SKILL.md names 1 domain. As links in the text: conventionalcommits.org. This is read from the text; nothing was executed.
Is Swpm Conventional Commits 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 Swpm Conventional Commits use?
Swpm Conventional Commits 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 Swpm Conventional Commits use?
About 1.6k tokens (SKILL.md is roughly 6.2k 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 Swpm Conventional Commits?
Skills that share tags, products or a category with Swpm Conventional Commits: Conventional Commit (jetstreamapp/jetstream, 126 stars), Git Commit Convention (7-e1even/learn-agent, 284 stars), Electron Multi-Process Architecture (iOfficeAI/AionUi, 33k stars) and Contextual Commit Messages (yamadashy/repomix, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Swpm Conventional Commits?
deinsoftware (a GitHub organization) maintains it in deinsoftware/swpm, which has 125 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on June 6, 2026.
Source: deinsoftware/swpm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.