Agent skill

Nvim Test

Execute tests and diagnose failures for love2d.nvim. An agent skill from S1M0N38/love2d.nvim.

MITAuto-check passedTesting & QA

Install Nvim Test

skills CLI

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

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

GitHub CLI

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

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-test -a codex

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

GitHub CLI

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

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

GitHub CLI

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

--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-test -a gemini-cli

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

GitHub CLI

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

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

At a glance

Execute tests and diagnose failures for love2d.nvim. An agent skill from S1M0N38/love2d.nvim.

Works in 4 steps: Read the error message — shows expected… → Check the line number — points to the… → Check for state leaks — if a test passes… → …
The user says run tests
SKILL.md covers Test stack, Running tests, Test files and Reading test output, plus 2 more sections
Calls make

What it does

Nvim Test is an agent skill from S1M0N38/love2d.nvim. Execute tests and diagnose failures for love2d.nvim. Use when the user says "run tests", "run the suite", or asks to execute the test suite (full or single file). Also use when the user pastes test error output, asks what a test failure means, or needs help fixing a broken test. The test stack is mini.test via lazy.minit with spec.lua files in tests/. Do not trigger for writing tests, learning test APIs, setting up testing from scratch, or non-Neovim tools.

Its SKILL.md is about 770 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 Testing & QA, covering Test generation and Failing and flaky tests. 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 says run tests
Asks to execute the test suite (full
The user pastes test error output
Asks what a test failure means

Example prompts

“run tests”
“run the suite”
“/nvim-test”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Read the error message — shows expected vs actual values
Check the line number — points to the failing assertion
Check for state leaks — if a test passes alone but fails in the suite,
Reproduce in isolation — make test-one MODULE=

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 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:
- make
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 Test loads about 770 tokens when it runs. Until then it costs about 118 tokens; SKILL.md has 254 words of instructions outside code blocks.

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

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

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

name: nvim-test
description: Execute tests and diagnose failures for love2d.nvim. Use when the user says "run tests", "run the suite", or asks to execute the test suite (full or single file). Also use when the user pastes test error output, asks what a test failure means, or needs help fixing a broken test. The test stack is mini.test via lazy.minit with *_spec.lua files in tests/. Do not trigger for writing tests, learning test APIs, setting up testing from scratch, or non-Neovim tools.

Running love2d.nvim Tests

This skill covers running tests and diagnosing failures.

Test stack

mini.test — Test framework (describe/it blocks, before_each/after_each)
lazy.minit — Bootstrap via tests/minit.lua (resolves mini.test + luassert)

Running tests

Full test suite

bash

make test
# or: nvim -l tests/minit.lua --minitest

Single test file

bash

make test-one MODULE=config
# or: nvim -l tests/minit.lua --minitest tests/config_spec.lua

Format check

bash

make lint

Full check (lint + test)

bash

make check

Test files

Each source module has a matching test file:

Test file	Module tested
`tests/config_spec.lua`	`love2d.config`
`tests/utils_spec.lua`	`love2d.utils`
`tests/init_spec.lua`	`love2d` (init)
`tests/events_spec.lua`	`love2d.events`
`tests/autocmd_spec.lua`	`love2d.autocmd`
`tests/lsp_spec.lua`	`love2d.lsp`
`tests/job_spec.lua`	`love2d.job`
`tests/output_spec.lua`	`love2d.output`
`tests/health_spec.lua`	`love2d.health`

Reading test output

mini.test reports with:

Green ✓ = passed
Red ✗ = failed (with error details below)
Summary line shows passed, failed, and total

Diagnosing failures

Read the error message — shows expected vs actual values
Check the line number — points to the failing assertion
Check for state leaks — if a test passes alone but fails in the suite, something didn't clean up (missing after_each)
Reproduce in isolation — make test-one MODULE=<name>

Common failure patterns

Error	Cause	Fix
`Expected: X, Got: Y`	Wrong return value	Check the function logic
`attempt to index nil value`	Module not loaded or config not set	Call `setup()` in `before_each`
`test passes alone, fails in suite`	State leak between tests	Add `after_each` cleanup, reset `did_setup`
`timeout / hangs`	`vim.wait` not resolving	Check async operations complete

Test conventions

Reset love2d.did_setup = false in before_each
Suppress notifications: override vim.notify in test files
Mock heavy side effects (jobstart, LSP, filesystem) — don't spawn real processes
Tests needing the love binary use pending() to skip gracefully

Project test files

tests/minit.lua — mini.test runner bootstrap
tests/*_spec.lua — Test files (one per module)
tests/demo-game/ — Realistic LÖVE game fixture

Files

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

Open the folder on GitHubat commit 2c31946

Compare with similar skills

Nvim Test 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 Test compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Nvim Test this skillS1M0N38/love2d.nvim	215	—	~770	Automated safety check: Pass	MIT	3 mo ago
Swig Testswig/swig	6.3k	—	~2.3k	Automated safety check: Pass	Custom licence	yesterday
Wioworkersio/skills	190	—	~5.8k	Automated safety check: Pass	MIT	2 mo ago
Caliber Testingcaliber-ai-org/ai-setup	1.3k	—	~3.2k	Automated safety check: Pass	MIT	14 days ago
Ue Test AuthoringJasonMa0012/MooaToon	749	—	~2.1k	Automated safety check: Notes	Custom licence	20 days ago
Minitest Ebt Luakokusenz/deltaview.nvim	127	—	~4k	Automated safety check: Pass	MIT	1 mo ago

Similar skills

Swig Test
swig/swig
Run SWIG test suite for specific languages. An agent skill from swig/swig.
6.3k GitHub stars~2.3k tokensUpdated yesterday
Testing & QAAuto-check passed
Wio
workersio/skills
Testing workflow skill for finding high-value test candidates, writing focused tests, generating realistic workloads, reviewing test value, and diagnosing test-suite health.
190 GitHub stars~5.8k tokensUpdated 2 mo ago
Testing & QAAuto-check passed
Caliber Testing
caliber-ai-org/ai-setup
Writes Vitest tests following project patterns: tests/ directories, vi.mock() for module mocking with vi.hoisted() for test-time factories, global LLM mock from src/test/setup.ts, environment…
1.3k GitHub stars~3.2k tokensUpdated 14 days ago
Testing & QAAuto-check passed
Ue Test Authoring
JasonMa0012/MooaToon
A skill your agent uses when writing or modifying UE automated tests (Automation, CQTest, Functional, Gauntlet, LowLevel) with Rider MCP available.
749 GitHub stars~2.1k tokensUpdated 20 days ago
Testing & QAAuto-check: notes
Minitest Ebt Lua
kokusenz/deltaview.nvim
This skill should be used when the user asks to write example-based tests, unit tests, or EBT for a Neovim plugin using the MiniTest (mini.test) framework in Lua.
127 GitHub stars~4k tokensUpdated 1 mo ago
Testing & QAAuto-check passed
Offload
imbue-ai/offload
Activate when you see offload.toml in a repo, offload referenced in build targets (justfile, Makefile, scripts), or when you need to run a large test suite in parallel.
125 GitHub stars~3.1k tokensUpdated 12 days ago
Testing & QAAuto-check passed

Questions about Nvim Test

What does Nvim Test do?

Execute tests and diagnose failures for love2d.nvim. An agent skill from S1M0N38/love2d.nvim. nvim.nvim.

When should I use Nvim Test?

Nvim Test fits situations like: the user says run tests; asks to execute the test suite (full; the user pastes test error output; asks what a test failure means.

How do I install Nvim Test in Claude Code?

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

How do I install Nvim Test in Codex?

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

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

What does Nvim Test need to run?

Going by SKILL.md and its folder, Nvim Test needs the command-line tools its instructions call (make).

Does Nvim Test access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Nvim Test 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 Nvim Test use?

Nvim Test 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 Nvim Test use?

About 770 tokens (SKILL.md is roughly 3.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 Nvim Test?

Skills that share tags, products or a category with Nvim Test: Swig Test (swig/swig, 6.3k stars), Wio (workersio/skills, 190 stars), Caliber Testing (caliber-ai-org/ai-setup, 1.3k stars) and Ue Test Authoring (JasonMa0012/MooaToon, 749 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nvim Test?

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 Test

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Running love2d.nvim Tests

Test stack

Running tests

Full test suite

Single test file

Format check

Full check (lint + test)

Test files

Reading test output

Diagnosing failures

Common failure patterns

Test conventions

Project test files

Files

Compare with similar skills

Similar skills

More from S1M0N38/love2d.nvim

Related

Questions about Nvim Test