Agent skill

Nvim Commit

Create conventional commits for love2d.nvim that are compatible with release-please and follow SemVer.

MITAuto-check: notesDevelopment

Install Nvim Commit

skills CLI

$ npx skills add S1M0N38/love2d.nvim --skill nvim-commit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install S1M0N38/love2d.nvim nvim-commit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/S1M0N38/love2d.nvim.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/nvim-commit .claude/skills/nvim-commit && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "nvim-commit" agent skill from https://github.com/S1M0N38/love2d.nvim/tree/main/.agents/skills/nvim-commit into .claude/skills/nvim-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvim-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

$skill-installer install https://github.com/S1M0N38/love2d.nvim/tree/main/.agents/skills/nvim-commit

Type 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.

skills CLI

$ npx skills add S1M0N38/love2d.nvim --skill nvim-commit -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install S1M0N38/love2d.nvim nvim-commit --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/S1M0N38/love2d.nvim.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/nvim-commit .agents/skills/nvim-commit && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "nvim-commit" agent skill from https://github.com/S1M0N38/love2d.nvim/tree/main/.agents/skills/nvim-commit into .agents/skills/nvim-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvim-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.

skills CLI

$ npx skills add S1M0N38/love2d.nvim --skill nvim-commit -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install S1M0N38/love2d.nvim nvim-commit --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/S1M0N38/love2d.nvim.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/nvim-commit .cursor/skills/nvim-commit && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "nvim-commit" agent skill from https://github.com/S1M0N38/love2d.nvim/tree/main/.agents/skills/nvim-commit into .cursor/skills/nvim-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvim-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

$ gemini skills install https://github.com/S1M0N38/love2d.nvim.git --path .agents/skills/nvim-commit

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add S1M0N38/love2d.nvim --skill nvim-commit -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install S1M0N38/love2d.nvim nvim-commit --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/S1M0N38/love2d.nvim.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/nvim-commit .gemini/skills/nvim-commit && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "nvim-commit" agent skill from https://github.com/S1M0N38/love2d.nvim/tree/main/.agents/skills/nvim-commit into .gemini/skills/nvim-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvim-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.

GitHub CLI

$ gh skill install S1M0N38/love2d.nvim nvim-commit

Installs 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).

skills CLI

$ npx skills add S1M0N38/love2d.nvim --skill nvim-commit -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/S1M0N38/love2d.nvim.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/nvim-commit .github/skills/nvim-commit && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "nvim-commit" agent skill from https://github.com/S1M0N38/love2d.nvim/tree/main/.agents/skills/nvim-commit into .github/skills/nvim-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvim-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.

skills CLI

$ npx skills add S1M0N38/love2d.nvim --skill nvim-commit -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install S1M0N38/love2d.nvim nvim-commit --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/S1M0N38/love2d.nvim.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/nvim-commit .opencode/skills/nvim-commit && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "nvim-commit" agent skill from https://github.com/S1M0N38/love2d.nvim/tree/main/.agents/skills/nvim-commit into .opencode/skills/nvim-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nvim-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: nvim-commit
GitHub stars: 215
Token cost: ~1.5k tokens
SKILL.md length: 439 words
Files: 1
Skills in repo: 5
Repo updated: Jul 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Create conventional commits for love2d.nvim that are compatible with release-please and follow SemVer.

Works in 4 steps: Analyze the diff → Stage files if needed → Determine type, scope, and description → …
The user asks to commit changes
SKILL.md covers Why this matters, Conventional Commit Format, Commit Types and SemVer Impact and Scopes for love2d.nvim, plus 5 more sections
Calls git

What it does

Nvim Commit is an agent skill from S1M0N38/love2d.nvim. Create conventional commits for love2d.nvim that are compatible with release-please and follow SemVer. Use when the user asks to commit changes, make a git commit, or says "/commit" while working on love2d.nvim. Analyzes the diff to produce correctly scoped, typed commit messages that release-please can parse into changelog entries and semantic version bumps.

Its SKILL.md is about 1.5k 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 Lua. The repository describes itself as: ♡ A simple Neovim plugin to build games with LÖVE. The licence is MIT.

When your agent uses it

The user asks to commit changes
Make a git commit
Says /commit while working on love2d.nvim

Example prompts

“/commit”
“/nvim-commit”

Requirements

Pre-approved tools (allowed-tools): Bash

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Analyze the diff
Stage files if needed
Determine type, scope, and description
Execute the commit

What it can do on your machine

Read from SKILL.md and the folder at commit 2c31946. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash
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

Nvim Commit loads about 1.5k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 439 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~93
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:120

**Never commit**: secrets, `.env`, credentials, private keys.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Bash
```

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 S1M0N38/love2d.nvim at commit 2c31946, republished under its MIT licence (© S1M0N38). 439 words, ~1,471 tokens.

Download SKILL.mdSave it as .claude/skills/nvim-commit/SKILL.md (or your agent's skills folder).

name: nvim-commit
description: Create conventional commits for love2d.nvim that are compatible with release-please and follow SemVer. Use when the user asks to commit changes, make a git commit, or says "/commit" while working on love2d.nvim. Analyzes the diff to produce correctly scoped, typed commit messages that release-please can parse into changelog entries and semantic version bumps.
allowed-tools: Bash
license: MIT

love2d.nvim Conventional Commits

Create semantic git commits for love2d.nvim that release-please can parse into changelog sections and correct version bumps.

Why this matters

release-please scans commit messages to decide what goes in the CHANGELOG and whether to bump the patch, minor, or major version. A poorly scoped or mistyped commit either gets ignored or ends up in the wrong changelog section.

Conventional Commit Format

<type>(<scope>): <description>

[optional body]

[optional footer(s)]

The scope is always present — Neovim plugins benefit from always scoping because modules are small and tightly named.

Commit Types and SemVer Impact

Type	Purpose	Version Bump	Changelog Section
`feat`	New feature or capability	minor	Features
`fix`	Bug fix	patch	Bug Fixes
`perf`	Performance improvement	patch	Performance
`refactor`	Code restructuring (no behavior)	none	(omitted)
`docs`	Documentation only	none	(omitted)
`style`	Formatting, whitespace (no logic)	none	(omitted)
`test`	Add or update tests	none	(omitted)
`build`	Build system, dependencies	none	Build
`ci`	CI configuration	none	CI
`chore`	Maintenance, tooling, meta	none	(omitted)
`revert`	Revert a previous commit	varies	Reverts

Scopes for love2d.nvim

The scope identifies the module or area that changed.

Auto-detecting scope from file paths

File Path Pattern	Scope
`lua/love2d/init.lua`	`init`
`lua/love2d/config.lua`	`config`
`lua/love2d/job.lua`	`job`
`lua/love2d/output.lua`	`output`
`lua/love2d/events.lua`	`events`
`lua/love2d/autocmd.lua`	`autocmd`
`lua/love2d/lsp.lua`	`lsp`
`lua/love2d/health.lua`	`health`
`lua/love2d/utils.lua`	`utils`
`lua/love2d/types.lua`	`types`
`plugin/love2d.lua`	`plugin`
`compiler/love.lua`	`compiler`
`doc/love2d.txt`	`docs`
`README.md`	`docs`
`tests/*_spec.lua`	omit scope
`after/queries/lua/injections.scm`	`injections`
`after/syntax/*`	`syntax`
`libraries/love2d/*`	`library`
`libraries/luasocket/*`	`library`
`.github/workflows/*`	`ci`
`.stylua.toml`, `.luarc.json`	omit scope

When multiple files span different scopes, pick the scope of the primary change.

Scope style

Lowercase, no hyphens or underscores
Examples: config, init, plugin, injections, library

Breaking Changes

Signal with ! after the type/scope:

feat(config)!: rename `disabled` to `enabled`

BREAKING CHANGE: `disabled` option renamed to `enabled` with inverted logic.

Workflow

1. Analyze the diff

bash

# Staged changes
git diff --staged

# If nothing staged, check working tree
git diff

# File list for scope detection
git diff --name-only --staged || git diff --name-only

Show full SKILL.md (174 more words)Show less

2. Stage files if needed

If nothing is staged, check git status --porcelain and stage the changed files. Group logically related changes together.

Never commit: secrets, .env, credentials, private keys.

3. Determine type, scope, and description

Type: based on the nature of the change
Scope: auto-detect from the file paths using the table above
Description: one line, present tense, imperative mood, under 72 characters

4. Execute the commit

bash

# Single line
git commit -m "feat(config): add output option for panel configuration"

# With body
git commit -m "$(cat <<'EOF'
feat(config): add makeprg support for LÖVE projects

Automatically configure makeprg and errorformat when a LÖVE
project is detected, allowing :make to run and parse errors.
EOF
)"

Writing good descriptions

Present tense, imperative mood: "add option" not "added option"
Start with lowercase after colon: feat(config): add debounce helper
Be specific: "add output option" beats "add new option"
Keep under 72 characters
Don't end with a period

What to avoid

Don't use chore for actual code changes — it won't appear in the changelog
Don't combine multiple unrelated changes in one commit
Don't use generic scopes like core or misc
Don't reference issue numbers in the subject line

Git Safety

Never update git config
Never run destructive commands (--force, hard reset) without explicit request
Never skip hooks (--no-verify) unless asked
Never force push to main/master

Files

Just SKILL.md in .agents/skills/nvim-commit of S1M0N38/love2d.nvim.

Open the folder on GitHubat commit 2c31946

Compare with similar skills

Nvim 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.

Nvim Commit compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Nvim Commit this skillS1M0N38/love2d.nvim	215	—	~1.5k	Automated safety check: Notes	MIT	3 mo ago
Contextual Commit Messagesyamadashy/repomix	29k	1 repos	~2.7k	Automated safety check: Pass	MIT	4 days ago
React Router Release Notes Prepremix-run/react-router	57k	—	~1.1k	Automated safety check: Pass	MIT	yesterday
Caveman Commitvishiri/fantasia-archive	409	13 repos	~642	Automated safety check: Pass	GPL-3.0	today
PR Finalize Reviewmicrosoft/garnet	12k	—	~3.1k	Automated safety check: Pass	MIT	today
ToolJet Multi-Repo CommitToolJet/ToolJet	41k	—	~1.3k	Automated safety check: Pass	AGPL-3.0	today

Similar skills

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.
29k GitHub starsUsed in 1 repo~2.7k tokens
DevelopmentAuto-check passed
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.
57k GitHub stars~1.1k tokensUpdated yesterday
DevelopmentAuto-check passed
Caveman Commit
vishiri/fantasia-archive
Ultra-compressed commit message generator. An agent skill from vishiri/fantasia-archive.
409 GitHub starsUsed in 13 repos~642 tokens
DevelopmentAuto-check passed
PR Finalize Review
microsoft/garnet
Official
Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.
12k GitHub stars~3.1k tokensUpdated today
DevelopmentAuto-check passed
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.
41k GitHub stars~1.3k tokensUpdated today
DevelopmentAuto-check passed
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.
103k GitHub starsUsed in 2 repos~3.5k tokens
DevelopmentAuto-check: notes

Questions about Nvim Commit

What does Nvim Commit do?

Create conventional commits for love2d.nvim that are compatible with release-please and follow SemVer. nvim.nvim that are compatible with release-please and follow SemVer.

When should I use Nvim Commit?

Nvim Commit fits situations like: the user asks to commit changes; make a git commit; says /commit while working on love2d.nvim.

How do I install Nvim Commit in Claude Code?

Run `npx skills add S1M0N38/love2d.nvim --skill nvim-commit -a claude-code`. Or copy the skill folder (.agents/skills/nvim-commit in S1M0N38/love2d.nvim) into .claude/skills/nvim-commit in your project. Claude Code loads it when a task matches its description.

How do I install Nvim Commit in Codex?

Run `npx skills add S1M0N38/love2d.nvim --skill nvim-commit -a codex`. Or copy the skill folder (.agents/skills/nvim-commit in S1M0N38/love2d.nvim) into .agents/skills/nvim-commit in your project. Codex loads it when a task matches its description.

Can I use Nvim 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 S1M0N38/love2d.nvim --skill nvim-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/nvim-commit, .gemini/skills/nvim-commit, .github/skills/nvim-commit and .opencode/skills/nvim-commit in your project.

What does Nvim Commit need to run?

Going by SKILL.md and its folder, Nvim Commit needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Bash.

Does Nvim 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 Nvim Commit safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file; pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Nvim Commit use?

Nvim Commit is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nvim Commit use?

About 1.5k tokens (SKILL.md is roughly 5.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 Nvim Commit?

Skills that share tags, products or a category with Nvim Commit: Contextual Commit Messages (yamadashy/repomix, 29k stars), React Router Release Notes Prep (remix-run/react-router, 57k stars), Caveman Commit (vishiri/fantasia-archive, 409 stars) and PR Finalize Review (microsoft/garnet, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nvim Commit?

S1M0N38 (a GitHub user) maintains it in S1M0N38/love2d.nvim, which has 215 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on July 7, 2026.

Source: S1M0N38/love2d.nvim on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Nvim Commit

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

love2d.nvim Conventional Commits

Why this matters

Conventional Commit Format

Commit Types and SemVer Impact

Scopes for love2d.nvim

Auto-detecting scope from file paths

Scope style

Breaking Changes

Workflow

1. Analyze the diff

2. Stage files if needed

3. Determine type, scope, and description

4. Execute the commit

Writing good descriptions

What to avoid

Git Safety

Files

Compare with similar skills

Similar skills

More from S1M0N38/love2d.nvim

Related

Questions about Nvim Commit