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

Consolidating Test Setup

by Comfy-Org in Comfy-Org/ComfyUI_frontend

Consolidates repeated test setup and teardown into the narrowest shared lifecycle owner.

GPL-3.0Auto-check passedTesting & QA

Install Consolidating Test Setup

skills CLI
$ npx skills add Comfy-Org/ComfyUI_frontend --skill consolidating-test-setup -a claude-code

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

GitHub CLI
$ gh skill install Comfy-Org/ComfyUI_frontend consolidating-test-setup --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/Comfy-Org/ComfyUI_frontend.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/consolidating-test-setup .claude/skills/consolidating-test-setup && 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
consolidating-test-setup
GitHub stars
2.1k
Token cost
~1.2k tokens
SKILL.md length
655 words
Files
3
Skills in repo
22
Repo updated
First seen
Licence
GPL-3.0

At a glance

Consolidates repeated test setup and teardown into the narrowest shared lifecycle owner.

  • Works in 6 steps: Discover → Classify → Challenge → …
  • Test files repeat initialization
  • SKILL.md covers Principles, Runner-specific guidance, Workflow and Report, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Consolidating Test Setup is an agent skill from Comfy-Org/ComfyUI_frontend. Consolidates repeated test setup and teardown into the narrowest shared lifecycle owner. Use when test files repeat initialization, cleanup, environment management, fixtures, or equivalent test doubles.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `reference/playwright.md` and `reference/vitest.md`).

It sits in Testing & QA, covering Unit testing. It works with Playwright and Vitest. The repository describes itself as: Official front-end implementation of ComfyUI. The licence is GPL-3.0.

When your agent uses it

  • Test files repeat initialization
  • Environment management
  • Equivalent test doubles

Example prompts

  • “Use the consolidating-test-setup skill to consolidate repeated test setup and teardown into the narrowest shared lifecycle owner”
  • “/consolidating-test-setup”

Workflow steps

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

  1. Discover
  2. Classify
  3. Challenge
  4. Place
  5. Migrate
  6. Prove

What it can do on your machine

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

    No scripts in the folder and no shell commands in SKILL.md.

    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

Consolidating Test Setup loads about 1.2k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 655 words of instructions outside code blocks.

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

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 Comfy-Org/ComfyUI_frontend at commit 03bca8a, republished under its GPL-3.0 licence (© Comfy-Org). 655 words, ~1,200 tokens.

Download SKILL.mdSave it as .claude/skills/consolidating-test-setup/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
consolidating-test-setup
description
Consolidates repeated test setup and teardown into the narrowest shared lifecycle owner. Use when test files repeat initialization, cleanup, environment management, fixtures, or equivalent test doubles.

Consolidating test setup

Move repeated test plumbing to the narrowest shared owner that can provide it reliably. Keep test files focused on behavior. The isolation and readability rules this skill applies are stated once in docs/guidance/testing-principles.md. This skill is the procedure.

Principles

Prove the code is equivalent

Repetition is evidence, not proof. Similar code may use different defaults, ordering, or lifetimes. Group candidates by behavior before treating them as duplicates.

Centralize invariants, not scenarios

Shared setup should establish conditions that hold for every test in its scope. State that explains one scenario belongs with that scenario.

Use the narrowest owner

Prefer the mechanism that already owns the lifecycle. Use runner configuration before hooks, scoped fixtures before global setup, and local setup for local requirements. Wider reuse is not better reuse.

Treat setup and teardown as one contract

Define who creates state, how long it lives, and who releases it. Cleanup must finish even when a test fails. Tests must not depend on execution order or on another test's cleanup.

A shared default should be deterministic and easy to override. Local exceptions must not weaken isolation elsewhere.

Subtract before abstracting

Remove suspected cargo-cult setup and run the affected tests. A targeted pass only marks it provisionally unnecessary. Delete it after the complete relevant suite and runner-specific lifecycle checks pass. If a test fails, use the failure to identify the contract before designing shared setup.

A helper must own a policy or lifecycle, or remove meaningful reader effort. Moving the same lines behind a new name is not an improvement.

Preserve test intent

Do not hide state that matters to the behavior under test. Check history before removing synchronization or cleanup because it may guard a past regression. Preserve that guarantee even if the implementation changes.

Runner-specific guidance

Load only the reference for the runner in use:

These references supplement the repository's testing guide. They do not replace it. Load both only when the task spans both runners.

Workflow

1. Discover

Read the runner configuration, setup files, fixtures, helpers, and test guidance. Count repeated lifecycle behavior and note the suites that use it.

2. Classify

For each candidate, record:

  • the state it owns
  • its lifetime and scope
  • whether it is an invariant or scenario detail
  • intentional differences between suites
  • behavior already supplied by the runner
Show full SKILL.md (257 more words)Show less
3. Challenge

Remove the candidate and run every affected suite. Classify it as unnecessary, universal, common with exceptions, or suite-specific.

Subagents may evaluate disjoint groups of suites. Require evidence and exception reports from each. Keep the design and integration decision in the parent task.

4. Place

Choose the required lifetime and scope first. Then use the simplest owner at that exact boundary:

  • native runner behavior that supports the required scope
  • existing shared setup, fixture, or hook
  • a focused helper or test double
  • the individual suite

Do not move state to a broader owner because its mechanism appears earlier in the list.

5. Migrate

Move one responsibility at a time. Add the shared owner, then remove only the local code it replaces. Keep intentional exceptions and scenario setup visible. Avoid unrelated test rewrites.

6. Prove

Run affected tests, tests of the shared lifecycle, repository static checks, and the complete relevant suite. Measure before and after when the new behavior runs for every test. Use enough comparable samples to separate a real change from normal variance.

Report

State the repeated contract, its new owner, retained exceptions, rejected alternatives, duplication removed, and validation results. Include performance evidence when shared setup could affect suite runtime.

Guardrails

  • Do not replace native runner behavior with a custom abstraction.
  • Do not widen setup scope without evidence.
  • Do not add a helper merely to move code.
  • Do not hide global mutable state behind helper indirection.
  • Do not trade visible test intent for shorter files.
  • Do not trust targeted tests alone after changing shared lifecycle behavior.

© Comfy-Org, 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

SKILL.md and 2 other files in .agents/skills/consolidating-test-setup of Comfy-Org/ComfyUI_frontend.

  • SKILL.md
  • reference/playwright.md
  • reference/vitest.md

Open the folder on GitHubat commit 03bca8a

Compare with similar skills

Consolidating Test Setup 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.

Consolidating Test Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Consolidating Test Setup this skillComfy-Org/ComfyUI_frontend2.1k—~1.2kAutomated safety check: PassGPL-3.0
Control UI E2Eopenclaw/openclaw392k—~2.9kAutomated safety check: PassMIT
Ckeditor5 TestingTriliumNext/Trilium38k—~3.3kAutomated safety check: PassAGPL-3.0
Check Visual Changesigrlk/storybook-addon-test-codegen1541 repos~1.4kAutomated safety check: PassMIT
Svelte Testingspences10/sveltest113—~579Automated safety check: PassMIT
Playwright Testingchongdashu/vibejam-starter-pack149—~2.1kAutomated safety check: PassNone

Similar skills

  • Control UI E2E

    openclaw/openclaw

    A skill your agent uses when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks…

    392k GitHub stars~2.9k tokensUpdated today
    Testing & QAAuto-check passed

  • Ckeditor5 Testing

    TriliumNext/Trilium

    Testing CKEditor 5 plugins in the Trilium monorepo. An agent skill from TriliumNext/Trilium.

    38k GitHub stars~3.3k tokensUpdated today
    Testing & QAAuto-check passed

  • Check Visual Changes

    igrlk/storybook-addon-test-codegen

    Check the visual impact of an edit mid-task with uiverify check — render just the components you're touching on the UI Verify fleet and diff them against the real CI baseline, without opening a PR…

    154 GitHub starsUsed in 1 repo~1.4k tokens
    Testing & QAAuto-check passed

  • Svelte Testing

    spences10/sveltest

    Fix and create Svelte 5 tests with vitest-browser-svelte and Playwright.

    113 GitHub stars~579 tokensUpdated today
    Testing & QAAuto-check passed

  • Playwright Testing

    chongdashu/vibejam-starter-pack

    Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.

    149 GitHub stars~2.1k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed

  • Ha Frontend Testing

    home-assistant/frontend

    Home Assistant frontend testing and validation workflow. An agent skill from home-assistant/frontend.

    5.7k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed

More from Comfy-Org/ComfyUI_frontend

All 22 skills in this repo

  • Adding Deprecation Warnings

    Comfy-Org/ComfyUI_frontend

    Adds deprecation warnings for renamed or removed properties/APIs.

    2.1k GitHub stars~775 tokensUpdated today
    Auto-check passed

  • Agent Integration Replay

    Comfy-Org/ComfyUI_frontend

    Replay recorded agent conversations as Playwright tests against the real chat panel and canvas.

    2.1k GitHub stars~805 tokensUpdated today
    Auto-check: notes

  • Codegen Transform

    Comfy-Org/ComfyUI_frontend

    Transforms raw Playwright codegen output into ComfyUI convention-compliant tests.

    2.1k GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Comment Sicko

    Comfy-Org/ComfyUI_frontend

    Dispatches the comment-sicko subagent to hunt gratuitous comments in a PR/diff, triages its raw findings, and posts a polite, professional writeup.

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

  • Hardening Flaky E2E Tests

    Comfy-Org/ComfyUI_frontend

    Diagnoses and fixes flaky Playwright e2e tests by replacing race-prone patterns with retry-safe alternatives.

    2.1k GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • Perf Fix With Proof

    Comfy-Org/ComfyUI_frontend

    Ships performance fixes with CI-proven improvement using stacked PRs.

    2.1k GitHub stars~1.6k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Consolidating Test Setup

What does Consolidating Test Setup do?

Consolidates repeated test setup and teardown into the narrowest shared lifecycle owner. Consolidating Test Setup is an agent skill from Comfy-Org/ComfyUI_frontend. Consolidates repeated test setup and teardown into the narrowest shared lifecycle owner.

When should I use Consolidating Test Setup?

Consolidating Test Setup fits situations like: test files repeat initialization; environment management; equivalent test doubles.

How do I install Consolidating Test Setup in Claude Code?

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

How do I install Consolidating Test Setup in Codex?

Run `npx skills add Comfy-Org/ComfyUI_frontend --skill consolidating-test-setup -a codex`. Or copy the skill folder (.agents/skills/consolidating-test-setup in Comfy-Org/ComfyUI_frontend) into .agents/skills/consolidating-test-setup in your project. Codex loads it when a task matches its description.

Can I use Consolidating Test Setup 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 Comfy-Org/ComfyUI_frontend --skill consolidating-test-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/consolidating-test-setup, .gemini/skills/consolidating-test-setup, .github/skills/consolidating-test-setup and .opencode/skills/consolidating-test-setup in your project.

What does Consolidating Test Setup need to run?

SKILL.md names no scripts, command-line tools or credentials: Consolidating Test Setup is instructions for the agent only.

Does Consolidating Test Setup 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 Consolidating Test Setup 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 Consolidating Test Setup use?

Consolidating Test Setup 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 Consolidating Test Setup use?

About 1.2k tokens (SKILL.md is roughly 4.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 Consolidating Test Setup?

Skills that share tags, products or a category with Consolidating Test Setup: Control UI E2E (openclaw/openclaw, 392k stars), Ckeditor5 Testing (TriliumNext/Trilium, 38k stars), Check Visual Changes (igrlk/storybook-addon-test-codegen, 154 stars) and Svelte Testing (spences10/sveltest, 113 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Consolidating Test Setup?

Comfy-Org (a GitHub organization) maintains it in Comfy-Org/ComfyUI_frontend, which has 2,055 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on October 8, 2026.

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