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.
Splits working tree changes into logical Git commits with conventional messages (feat, fix, test, chore, refactor, style, docs).
Install Git Conventional Commits
$ npx skills add vishiri/fantasia-archive --skill git-conventional-commits -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vishiri/fantasia-archive git-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/vishiri/fantasia-archive.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/git-conventional-commits .claude/skills/git-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 "git-conventional-commits" agent skill from https://github.com/vishiri/fantasia-archive/tree/master/.cursor/skills/git-conventional-commits into .claude/skills/git-conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-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/vishiri/fantasia-archive/tree/master/.cursor/skills/git-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 vishiri/fantasia-archive --skill git-conventional-commits -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vishiri/fantasia-archive git-conventional-commits --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vishiri/fantasia-archive.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/git-conventional-commits .agents/skills/git-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 "git-conventional-commits" agent skill from https://github.com/vishiri/fantasia-archive/tree/master/.cursor/skills/git-conventional-commits into .agents/skills/git-conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-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 vishiri/fantasia-archive --skill git-conventional-commits -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vishiri/fantasia-archive git-conventional-commits --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vishiri/fantasia-archive.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/git-conventional-commits .cursor/skills/git-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 "git-conventional-commits" agent skill from https://github.com/vishiri/fantasia-archive/tree/master/.cursor/skills/git-conventional-commits into .cursor/skills/git-conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-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/vishiri/fantasia-archive.git --path .cursor/skills/git-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 vishiri/fantasia-archive --skill git-conventional-commits -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vishiri/fantasia-archive git-conventional-commits --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vishiri/fantasia-archive.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/git-conventional-commits .gemini/skills/git-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 "git-conventional-commits" agent skill from https://github.com/vishiri/fantasia-archive/tree/master/.cursor/skills/git-conventional-commits into .gemini/skills/git-conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-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 vishiri/fantasia-archive git-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 vishiri/fantasia-archive --skill git-conventional-commits -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vishiri/fantasia-archive.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/git-conventional-commits .github/skills/git-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 "git-conventional-commits" agent skill from https://github.com/vishiri/fantasia-archive/tree/master/.cursor/skills/git-conventional-commits into .github/skills/git-conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-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 vishiri/fantasia-archive --skill git-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 vishiri/fantasia-archive git-conventional-commits --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vishiri/fantasia-archive.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/git-conventional-commits .opencode/skills/git-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 "git-conventional-commits" agent skill from https://github.com/vishiri/fantasia-archive/tree/master/.cursor/skills/git-conventional-commits into .opencode/skills/git-conventional-commits/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-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
git-conventional-commits- GitHub stars
- 409
- Token cost
- ~730 tokens
- SKILL.md length
- 252 words
- Files
- 1
- Skills in repo
- 35
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Splits working tree changes into logical Git commits with conventional messages (feat, fix, test, chore, refactor, style, docs).
- Works in 7 steps: Inspect: git status, git diff, git diff… → Full quality gate: yarn testbatch:verify… → Storybook gate: changed… → …
- The user asks to commit
- SKILL.md covers Allowed types, Workflow (default when user…, Rules and Final cleanup override, plus 2 more sections
- Calls git and yarn
What it does
Git Conventional Commits is an agent skill from vishiri/fantasia-archive. Splits working tree changes into logical Git commits with conventional messages (feat, fix, test, chore, refactor, style, docs). Proposes commits one at a time and waits for explicit user approval before each git commit. Use when the user asks to commit, split commits, stage by topic, or use conventional / semantic commit messages.
Its SKILL.md is about 730 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 Git. The repository describes itself as: A world-builder's best friend! The licence is GPL-3.0.
When your agent uses it
- The user asks to commit
- Use conventional / semantic commit messages
Example prompts
- “Use the git-conventional-commits skill to split working tree changes into logical Git commits with conventional messages (feat, fix, test, chore…”
- “/git-conventional-commits”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Inspect: git status, git diff, git diff --staged
- Full quality gate: yarn testbatch:verify one terminal (testing-terminal-isolation.mdc). Dev scoped gate during edits does not substitute…
- Storybook gate: changed src/components/** — stories/mocks. Skip changelog-only repair
- Changelog gate: update changeLog.md before commit; prefer same commit as product work — fantasia-changelog-en-us
- Plan: ordered commits — type + subject + paths
- Approval loop (when user asked per-commit approval): present next commit → wait explicit OK → git add those paths only → git commit
- Single commit / no step-by-step: valid type: message after gates
What it can do on your machine
Read from SKILL.md and the folder at commit 26d4648. 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:
gityarn
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and yarn, 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
Git Conventional Commits loads about 730 tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 252 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 vishiri/fantasia-archive at commit 26d4648, republished under its GPL-3.0 licence (© vishiri). 252 words, ~730 tokens.
Download SKILL.mdSave it as
.claude/skills/git-conventional-commits/SKILL.md (or your agent's skills folder).- name
- git-conventional-commits
- description
- Splits working tree changes into logical Git commits with conventional messages (feat, fix, test, chore, refactor, style, docs). Proposes commits one at a time and waits for explicit user approval before each git commit. Use when the user asks to commit, split commits, stage by topic, or use conventional / semantic commit messages.
Conventional commits — logical splits and approval loop
Allowed types
Exactly one: feat | fix | test | chore | refactor | style | docs.
| Type | Use for |
|---|---|
feat | New user-visible behavior |
fix | Bug fixes |
test | Tests only |
chore | Deps, CI, tooling, housekeeping |
refactor | Restructure, same behavior |
style | Format/lint autofix, no logic |
docs | README, AGENTS, rules/skills, doc comments |
Format: type: imperative subject — lowercase type, space after colon, ~72 chars, no trailing period.
Local enforcement: .husky/commit-msg → yarn lint:commit. git commit --no-verify only when must bypass hooks.
Workflow (default when user wants multiple commits)
- Inspect:
git status,git diff,git diff --staged - Full quality gate:
yarn testbatch:verifyone terminal (testing-terminal-isolation.mdc). Dev scoped gate during edits does not substitute. Changelog-only exception: onlyi18n/*/documents/changeLog.md+ full gate already passed after substantive edits - Storybook gate: changed
src/components/**— stories/mocks. Skip changelog-only repair - Changelog gate: update
changeLog.mdbefore commit; prefer same commit as product work — fantasia-changelog-en-us - Plan: ordered commits — type + subject + paths
- Approval loop (when user asked per-commit approval): present next commit → wait explicit OK →
git addthose paths only →git commit - Single commit / no step-by-step: valid
type:message after gates
Rules
- Never commit without approval when user requested per-commit approval
- Never mix unrelated concerns in one commit
- Prefer small reviewable chunks
refactorfor production moves;chorefor repo/meta- No skipping changelog for substantive work
- No skipping Storybook for
src/components/**product commits
Final cleanup override
Final cleanup → fantasia-final-cleanup: verify, changelog, logical commits, push — may commit without per-commit approval unless user interrupts.
Related
Types
Shared types → types/. See types-folder.mdc.
© vishiri, 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 .cursor/skills/git-conventional-commits of vishiri/fantasia-archive.
Open the folder on GitHubat commit 26d4648
Compare with similar skills
Git 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 |
|---|---|---|---|---|---|---|
| Git Conventional Commits this skillvishiri/fantasia-archive | 409 | — | ~730 | Automated safety check: Pass | GPL-3.0 | |
| React Router Release Notes Prepremix-run/react-router | 57k | — | ~1.1k | 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 | 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 | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
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 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.
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
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.
More from vishiri/fantasia-archive
All 35 skills in this repoCaveman Commit
vishiri/fantasia-archive
Ultra-compressed commit message generator. An agent skill from vishiri/fantasia-archive.
Caveman Review
vishiri/fantasia-archive
Ultra-compressed code review comments. An agent skill from vishiri/fantasia-archive.
Caveman Compress
vishiri/fantasia-archive
Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens.
Cavecrew
vishiri/fantasia-archive
Decision guide for delegating to caveman-style subagents. An agent skill from vishiri/fantasia-archive.
Caveman Help
vishiri/fantasia-archive
Quick-reference card for all caveman modes, skills, and commands.
Fantasia Context Menu Dividers
vishiri/fantasia-archive
Context menu divider policy: full primary-bright group separators vs low-opacity separatorAlt between consecutive items in the same group.
Related
Works with
Categories
Questions about Git Conventional Commits
What does Git Conventional Commits do?
Splits working tree changes into logical Git commits with conventional messages (feat, fix, test, chore, refactor, style, docs). Git Conventional Commits is an agent skill from vishiri/fantasia-archive. Splits working tree changes into logical Git commits with conventional messages (feat, fix, test, chore, refactor, style, docs).
When should I use Git Conventional Commits?
Git Conventional Commits fits situations like: the user asks to commit; use conventional / semantic commit messages.
How do I install Git Conventional Commits in Claude Code?
Run `npx skills add vishiri/fantasia-archive --skill git-conventional-commits -a claude-code`. Or copy the skill folder (.cursor/skills/git-conventional-commits in vishiri/fantasia-archive) into .claude/skills/git-conventional-commits in your project. Claude Code loads it when a task matches its description.
How do I install Git Conventional Commits in Codex?
Run `npx skills add vishiri/fantasia-archive --skill git-conventional-commits -a codex`. Or copy the skill folder (.cursor/skills/git-conventional-commits in vishiri/fantasia-archive) into .agents/skills/git-conventional-commits in your project. Codex loads it when a task matches its description.
Can I use Git 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 vishiri/fantasia-archive --skill git-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/git-conventional-commits, .gemini/skills/git-conventional-commits, .github/skills/git-conventional-commits and .opencode/skills/git-conventional-commits in your project.
What does Git Conventional Commits need to run?
Going by SKILL.md and its folder, Git Conventional Commits needs the command-line tools its instructions call (git and yarn).
Does Git Conventional Commits 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 Git 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 Git Conventional Commits use?
Git Conventional Commits 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 Conventional Commits use?
About 730 tokens (SKILL.md is roughly 2.9k 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 Conventional Commits?
Skills that share tags, products or a category with Git Conventional Commits: React Router Release Notes Prep (remix-run/react-router, 57k stars), ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 103k stars) and React Router Pull Request Creator (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Git Conventional Commits?
vishiri (a GitHub user) maintains it in vishiri/fantasia-archive, which has 409 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 7, 2026.
Source: vishiri/fantasia-archive on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.