New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Run Area Tests

by genex-games in genex-games/genex-desktop

Pick and run only the tests a change can affect - the affected-tests selector, one knowledge-map area, or named files - instead of the full suite.

MITAuto-check passedTesting & QA

Install Run Area Tests

skills CLI
$ npx skills add genex-games/genex-desktop --skill run-area-tests -a claude-code

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

GitHub CLI
$ gh skill install genex-games/genex-desktop run-area-tests --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/genex-games/genex-desktop.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/run-area-tests .claude/skills/run-area-tests && 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/

Facts

Skill name
run-area-tests
GitHub stars
467
Token cost
~698 tokens
SKILL.md length
266 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Pick and run only the tests a change can affect - the affected-tests selector, one knowledge-map area, or named files - instead of the full suite.

  • Testing & QA work in your project
  • SKILL.md covers Selector, Area and named files and Rules
  • Calls node, npm and git

What it does

Run Area Tests is an agent skill from genex-games/genex-desktop. Pick and run only the tests a change can affect - the affected-tests selector, one knowledge-map area, or named files - instead of the full suite. Use after each red/green step and before finishing a task step.

Its SKILL.md is about 700 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. It works with npm. The repository describes itself as: Desktop app for game dev with AI. macOS and Linux, Windows soon. The licence is MIT.

When your agent uses it

  • Testing & QA work in your project

Example prompts

  • “/run-area-tests”

What it can do on your machine

Read from SKILL.md and the folder at commit b13cc77. 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:

    • node
    • npm
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm and 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

Run Area Tests loads about 698 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 266 words of instructions outside code blocks.

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

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 genex-games/genex-desktop at commit b13cc77, republished under its MIT licence (© genex-games). 266 words, ~698 tokens.

Download SKILL.mdSave it as .claude/skills/run-area-tests/SKILL.md (or your agent's skills folder).
name
run-area-tests
description
Pick and run only the tests a change can affect - the affected-tests selector, one knowledge-map area, or named files - instead of the full suite. Use after each red/green step and before finishing a task step.

Run the affected and area tests

Choose the cheapest layer that proves the behaviour; see docs/agent/verification.md for the full L0-L5 table. Never describe a focused pass as a full-suite pass.

The scope table owns required checks. Its layer catalog describes available commands, not a cumulative checklist. For bounded core/harness/engine changes, run the affected L3 suites; harness changes also need the incident gate. Reserve full verification for broad integration changes or explicit requests.

Selector

scripts/affected-tests.mjs is read-only. It takes changed files from git diff against the merge-base with origin/dev plus untracked files, walks each test's import graph, and merges explicit edges from tests/test-map.json.

sh
node scripts/affected-tests.mjs                     # list L1 (pure) and L3 (rig) tests
node scripts/affected-tests.mjs --json              # machine-readable selection
node scripts/affected-tests.mjs --run               # run L1 in parallel, L3 serially
node scripts/affected-tests.mjs --tier L1 --run     # skip the slow rig group while iterating
node scripts/affected-tests.mjs --files src/shared/chat-activity.ts --run
node scripts/affected-tests.mjs --staged --run      # only what is staged

Rig tests (anything reaching tests/helpers/studio-rig.ts) are L3 and run with --test-concurrency=1. A change under src/harness-seed/** or src/game-template/** also selects the harness gate (harness-incidents and scoreboard), because rigs copy those folders instead of importing them.

Area and named files

  • Area ids with their docs and sources: docs/agent/knowledge-map.json; npm run review:context -- --area <id> lists the docs and checks for one area.
  • One or more files: npm test -- tests/conformance/<name>.test.ts [more files].
  • One behaviour while iterating: npm test -- --test-name-pattern='<test name>' tests/conformance/<name>.test.ts.

Rules

  • Red first: run the new or changed test and see it fail for the right reason.
  • A selector that picks nothing for a behaviour change means a test or a tests/test-map.json edge is missing; add it rather than skipping verification.
  • On failure keep the log, decide whether product, expectation, fixture or environment is wrong, and rerun only after a specific change. Never raise deadlines to get green.
  • Full npm test / npm run verify only for broad changes or when asked.
  • Report which layers and files ran.

© genex-games, 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/run-area-tests of genex-games/genex-desktop.

Open the folder on GitHubat commit b13cc77

Compare with similar skills

Run Area Tests 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.

Run Area Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Run Area Tests this skillgenex-games/genex-desktop467—~698Automated safety check: PassMIT
OpenHarness End-to-End EvalsHKUDS/OpenHarness16k1 repos~2.1kAutomated safety check: NotesMIT
Qwen Code E2E TestingQwenLM/qwen-code28k—~2.1kAutomated safety check: PassApache-2.0
Quality Scandiegosouzapw/OmniRoute74k—~748Automated safety check: PassMIT
E2E TestingInsForge/InsForge13k—~1.5kAutomated safety check: PassApache-2.0
Analogjsanalogjs/analog3.2k—~891Automated safety check: PassMIT

Similar skills

  • OpenHarness End-to-End Evals

    HKUDS/OpenHarness

    Validates OpenHarness features by running real multi-turn agent loops with live LLM calls against an unfamiliar codebase, checking actual tool execution.

    16k GitHub starsUsed in 1 repo~2.1k tokens
    Testing & QAAuto-check: notes

  • Qwen Code E2E Testing

    QwenLM/qwen-code

    Guides end-to-end testing of the Qwen Code CLI in headless mode with real model calls, MCP test servers and inspection of raw API traffic.

    28k GitHub stars~2.1k tokensUpdated today
    Testing & QAAuto-check passed

  • Quality Scan

    diegosouzapw/OmniRoute

    Runs a scoped, read-only quality scan on a repository candidate and reports exact evidence, failures and frozen debt, without treating a static scan as release acceptance.

    74k GitHub stars~748 tokensUpdated today
    Testing & QAAuto-check passed

  • E2E Testing

    InsForge/InsForge

    A skill your agent uses when an InsForge maintainer has finished an OSS repo change and is ready to open, update, or submit the InsForge PR.

    13k GitHub stars~1.5k tokensUpdated 2 days ago
    Testing & QAAuto-check passed

  • Analogjs

    analogjs/analog

    Conventions for working in an AnalogJS app (an Angular meta-framework powered by Vite) — file-based routing with .page.ts files, RouteMeta, server and API routes on Nitro/h3, page load functions and…

    3.2k GitHub stars~891 tokensUpdated today
    Testing & QAAuto-check passed

  • RStudio Playwright Test Runner

    rstudio/rstudio

    Runs RStudio's Playwright end-to-end tests against the desktop app or a server build with the project's npm scripts, asking you which mode to use first.

    5.1k GitHub stars~801 tokensUpdated today
    Testing & QAAuto-check passed

More from genex-games/genex-desktop

  • Add Event Type

    genex-games/genex-desktop

    Add a new persisted event (custom eventtype in the append-only log) or a transient UI event, with its producer, readers and tests.

    467 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Add Ipc Channel

    genex-games/genex-desktop

    Add or change a renderer-to-main IPC channel (a new window.studio call) end to end - main handler, preload, typed API, fixture classification and tests.

    467 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Add Plugin Tool

    genex-games/genex-desktop

    Add or change an agent-callable tool contributed by a Studio plugin (manifest declaration, backend handler, consent, docs and tests).

    467 GitHub stars~841 tokensUpdated today
    Auto-check passed

  • Harness Incident Fix

    genex-games/genex-desktop

    Fix a bug in the in-app harness loop (src/harness-seed/) test-first - write the incident row that reproduces it, see it fail, fix, then run the harness gate.

    467 GitHub stars~843 tokensUpdated today
    Auto-check passed

  • Break

    genex-games/genex-desktop

    Renders a component you choose in every state and scenario on a temporary page and stress tests it.

    467 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

  • Verify UI Via Dev Control

    genex-games/genex-desktop

    Verify renderer, IPC, preview or startup changes through owned studio:dev profiles, or hand off the real app for manual testing.

    467 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Run Area Tests

What does Run Area Tests do?

Pick and run only the tests a change can affect - the affected-tests selector, one knowledge-map area, or named files - instead of the full suite. Run Area Tests is an agent skill from genex-games/genex-desktop. Pick and run only the tests a change can affect - the affected-tests selector, one knowledge-map area, or named files - instead of the full suite.

When should I use Run Area Tests?

Run Area Tests fits situations like: testing & QA work in your project.

How do I install Run Area Tests in Claude Code?

Run `npx skills add genex-games/genex-desktop --skill run-area-tests -a claude-code`. Or copy the skill folder (.agents/skills/run-area-tests in genex-games/genex-desktop) into .claude/skills/run-area-tests in your project. Claude Code loads it when a task matches its description.

How do I install Run Area Tests in Codex?

Run `npx skills add genex-games/genex-desktop --skill run-area-tests -a codex`. Or copy the skill folder (.agents/skills/run-area-tests in genex-games/genex-desktop) into .agents/skills/run-area-tests in your project. Codex loads it when a task matches its description.

Can I use Run Area Tests 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 genex-games/genex-desktop --skill run-area-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/run-area-tests, .gemini/skills/run-area-tests, .github/skills/run-area-tests and .opencode/skills/run-area-tests in your project.

What does Run Area Tests need to run?

Going by SKILL.md and its folder, Run Area Tests needs the command-line tools its instructions call (node, npm and git).

Does Run Area Tests access the network?

SKILL.md contains no URLs. Its commands use npm and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Run Area Tests 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 Run Area Tests use?

Run Area Tests 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 Run Area Tests use?

About 698 tokens (SKILL.md is roughly 2.8k 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 Run Area Tests?

Skills that share tags, products or a category with Run Area Tests: OpenHarness End-to-End Evals (HKUDS/OpenHarness, 16k stars), Qwen Code E2E Testing (QwenLM/qwen-code, 28k stars), Quality Scan (diegosouzapw/OmniRoute, 74k stars) and E2E Testing (InsForge/InsForge, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Run Area Tests?

genex-games (a GitHub organization) maintains it in genex-games/genex-desktop, which has 467 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 8, 2026.

Source: genex-games/genex-desktop on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.