Test Commander
EliasOulkadi/shokunin
Generate unit, integration, E2E, and visual regression tests following the Testing Trophy methodology (80% integration).
Guide to Playwright visual regression tests in Handsontable: when a screenshot is justified, the tablePage fixture, naming, reg-suit comparison and demo routes.
Install Handsontable Visual Testing
$ npx skills add handsontable/handsontable --skill visual-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install handsontable/handsontable visual-testing --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/handsontable/handsontable.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/visual-testing .claude/skills/visual-testing && 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 "visual-testing" agent skill from https://github.com/handsontable/handsontable/tree/develop/.claude/skills/visual-testing into .claude/skills/visual-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "visual-testing", 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/handsontable/handsontable/tree/develop/.claude/skills/visual-testingType 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 handsontable/handsontable --skill visual-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install handsontable/handsontable visual-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/handsontable/handsontable.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/visual-testing .agents/skills/visual-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "visual-testing" agent skill from https://github.com/handsontable/handsontable/tree/develop/.claude/skills/visual-testing into .agents/skills/visual-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "visual-testing", 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 handsontable/handsontable --skill visual-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install handsontable/handsontable visual-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/handsontable/handsontable.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/visual-testing .cursor/skills/visual-testing && 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 "visual-testing" agent skill from https://github.com/handsontable/handsontable/tree/develop/.claude/skills/visual-testing into .cursor/skills/visual-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "visual-testing", 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/handsontable/handsontable.git --path .claude/skills/visual-testing--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 handsontable/handsontable --skill visual-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install handsontable/handsontable visual-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/handsontable/handsontable.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/visual-testing .gemini/skills/visual-testing && 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 "visual-testing" agent skill from https://github.com/handsontable/handsontable/tree/develop/.claude/skills/visual-testing into .gemini/skills/visual-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "visual-testing", 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 handsontable/handsontable visual-testingInstalls 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 handsontable/handsontable --skill visual-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/handsontable/handsontable.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/visual-testing .github/skills/visual-testing && 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 "visual-testing" agent skill from https://github.com/handsontable/handsontable/tree/develop/.claude/skills/visual-testing into .github/skills/visual-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "visual-testing", 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 handsontable/handsontable --skill visual-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install handsontable/handsontable visual-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/handsontable/handsontable.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/visual-testing .opencode/skills/visual-testing && 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 "visual-testing" agent skill from https://github.com/handsontable/handsontable/tree/develop/.claude/skills/visual-testing into .opencode/skills/visual-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "visual-testing", 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
visual-testing- GitHub stars
- 22k
- Token cost
- ~2.3k tokens
- SKILL.md length
- 1,031 words
- Files
- 1
- Skills in repo
- 31
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Guide to Playwright visual regression tests in Handsontable: when a screenshot is justified, the tablePage fixture, naming, reg-suit comparison and demo routes.
- Writing a Playwright visual regression test for a Handsontable feature
- SKILL.md covers Decision rule, Custom fixture: tablePage, Test naming and Screenshot workflow, plus 6 more sections
- Calls npm
- Adding a demo route so a new feature can be captured
What it does
Visual tests live in the visual-tests folder as Playwright and TypeScript specs, and reg-suit compares their screenshots with golden records. Two jobs are covered: adding a visual test for an existing demo route, and adding a new feature demo route to the js demo under examples/next/visual-tests before writing its test. The documentation examples tree is not served by the visual suite.
A decision rule limits captures. A screenshot proves pixels only, so each distinct visual state gets one capture, asserted first, while focus, selection, data and menu facts stay as Playwright assertions in the E2E tests, and a visual spec is added to those assertions, never instead of them. Specs import the custom visualTest runner, since a bare test call is a lint error. The tablePage fixture opens the demo page, waits for the table, disables CSS animations and clears stray text selections before each capture, and file names are kebab-case descriptions of the visual state.
When your agent uses it
- Writing a Playwright visual regression test for a Handsontable feature
- Adding a demo route so a new feature can be captured
- Deciding whether a behavior deserves a screenshot at all
Example prompts
- “Add a visual test for the nested header class name feature using the tablePage fixture.”
- “Create a demo route for the new row hiding feature and a visual spec for it.”
- “Does selecting a cell need a screenshot, or is an assertion enough?”
Requirements
- A checkout of the Handsontable repository
- Playwright
What it can do on your machine
Read from SKILL.md and the folder at commit 68b5e97. 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:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, 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
Handsontable Visual Testing loads about 2.3k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 1,031 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 1,031 words (~2,325 tokens).
“Visual tests live in visual-tests/ (Playwright + TypeScript); reg-suit compares screenshots against golden records. Two workflows: (a) add a visual test for an existing demo route, (b) add a new /-demo route to the js demo in examples/next/visual-tests/js/demo/ (the creating-visual-test-examples…”
- name
- visual-testing
- path
- visual-tests/**
Files
Just SKILL.md in .claude/skills/visual-testing of handsontable/handsontable.
Open the folder on GitHubat commit 68b5e97
Compare with similar skills
Handsontable Visual Testing 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 |
|---|---|---|---|---|---|---|
| Handsontable Visual Testing this skillhandsontable/handsontable | 22k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Test CommanderEliasOulkadi/shokunin | 114 | — | ~3k | Automated safety check: Notes | MIT | |
| Playwright Automationpetrkindlmann/qa-skills | 163 | — | ~5.5k | Automated safety check: Pass | MIT | |
| UI Visual DebuggingNangoHQ/nango | 13k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Computed Stylesbitovi/ai-enablement-prompts | 121 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Dozzle Visual Snapshot Updateramir20/dozzle | 15k | — | ~797 | Automated safety check: Pass | MIT |
Similar skills
Playwright Automation
petrkindlmann/qa-skills
Write production-grade Playwright tests in TypeScript: Page Object Model, fixtures, auto-waiting, user-facing locators, parallel execution, CI integration, sharding, and 2025-2026 feature awareness.
UI Visual Debugging
NangoHQ/nango
A skill your agent uses when modifying or visually debugging Nango frontend UI, including packages/webapp, packages/connect-ui, browser interactions, screenshots, and visual regressions.
Computed Styles
bitovi/ai-enablement-prompts
Extract and compare computed CSS styles between a baseline URL and a dev/Storybook URL using Playwright MCP evaluate calls.
Dozzle Visual Snapshot Updater
amir20/dozzle
Regenerates Playwright visual snapshots for Dozzle after an intentional UI change, running them through Docker Compose so filenames match the Linux CI platform.
RStudio Selenium to Playwright Migration
rstudio/rstudio
Converts RStudio Python Selenium electron tests into TypeScript Playwright tests, checking each against a live RStudio before counting it as migrated.
More from handsontable/handsontable
All 31 skills in this repoHandsontable Playwright E2E Tests
handsontable/handsontable
Guides writing and changing Playwright end-to-end tests for Handsontable using page objects, data-testid hooks and deterministic waits.
Handsontable Angular Wrapper Development
handsontable/handsontable
Guides changes to the @handsontable/angular-wrapper package: the HotTableComponent lifecycle, NgZone performance handling, settings services and the ng-packagr build.
BrowserStack Live Testing
handsontable/handsontable
Opens a live BrowserStack session on a real Android, iOS or desktop browser for a local or public URL, tunneling localhost through Cloudflare when needed.
Handsontable Changelog Entry
handsontable/handsontable
Decides whether a code change needs a changelog entry and creates the JSON file in .changelogs with the right type, framework and user-facing title.
Code Review Graph Navigator
handsontable/handsontable
Queries a pre-built, Tree-sitter-based code graph of the whole monorepo instead of grepping call chains, for exploring, debugging, refactoring or reviewing code.
Handsontable Coordinate Systems
handsontable/handsontable
Explains Handsontable's physical, visual and renderable row and column coordinate spaces and how to convert between them with IndexMapper, for debugging misplaced rows or columns.
Related
Works with
Categories
Questions about Handsontable Visual Testing
What does Handsontable Visual Testing do?
Guide to Playwright visual regression tests in Handsontable: when a screenshot is justified, the tablePage fixture, naming, reg-suit comparison and demo routes. Visual tests live in the visual-tests folder as Playwright and TypeScript specs, and reg-suit compares their screenshots with golden records. Two jobs are covered: adding a visual test for an existing demo route, and adding a new feature demo route to the js demo under examples/next/visual-tests before writing its test.
When should I use Handsontable Visual Testing?
Handsontable Visual Testing fits situations like: writing a Playwright visual regression test for a Handsontable feature; adding a demo route so a new feature can be captured; deciding whether a behavior deserves a screenshot at all.
How do I install Handsontable Visual Testing in Claude Code?
Run `npx skills add handsontable/handsontable --skill visual-testing -a claude-code`. Or copy the skill folder (.claude/skills/visual-testing in handsontable/handsontable) into .claude/skills/visual-testing in your project. Claude Code loads it when a task matches its description.
How do I install Handsontable Visual Testing in Codex?
Run `npx skills add handsontable/handsontable --skill visual-testing -a codex`. Or copy the skill folder (.claude/skills/visual-testing in handsontable/handsontable) into .agents/skills/visual-testing in your project. Codex loads it when a task matches its description.
Can I use Handsontable Visual Testing 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 handsontable/handsontable --skill visual-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/visual-testing, .gemini/skills/visual-testing, .github/skills/visual-testing and .opencode/skills/visual-testing in your project.
What does Handsontable Visual Testing need to run?
Going by SKILL.md and its folder, Handsontable Visual Testing needs the command-line tools its instructions call (npm). Our summary lists: A checkout of the Handsontable repository; Playwright.
Does Handsontable Visual Testing access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Handsontable Visual Testing 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 Handsontable Visual Testing use?
Handsontable Visual Testing 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 Handsontable Visual Testing use?
About 2.3k tokens (SKILL.md is roughly 9.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 Handsontable Visual Testing?
Skills that share tags, products or a category with Handsontable Visual Testing: Test Commander (EliasOulkadi/shokunin, 114 stars), Playwright Automation (petrkindlmann/qa-skills, 163 stars), UI Visual Debugging (NangoHQ/nango, 13k stars) and Computed Styles (bitovi/ai-enablement-prompts, 121 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Handsontable Visual Testing?
handsontable (a GitHub organization) maintains it in handsontable/handsontable, which has 22,059 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 7, 2026.
Source: handsontable/handsontable on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.