Agent skill

Test Coverage

by scott-fryxell in scott-fryxell/brayness

Write Vitest specs for Vue 3 JavaScript (Vite Plus, happy-dom, @vue/test-utils) and analyze V8 coverage + Fallow health to prioritize test-first refactors.

MITAuto-check passedTesting & QA

Install Test Coverage

skills CLI

$ npx skills add scott-fryxell/brayness --skill test-coverage -a claude-code

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

GitHub CLI

$ gh skill install scott-fryxell/brayness test-coverage --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/scott-fryxell/brayness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/test-coverage .claude/skills/test-coverage && 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 "test-coverage" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/test-coverage into .claude/skills/test-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-coverage", 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/scott-fryxell/brayness/tree/main/skills/test-coverage

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 scott-fryxell/brayness --skill test-coverage -a codex

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

GitHub CLI

$ gh skill install scott-fryxell/brayness test-coverage --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/scott-fryxell/brayness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/test-coverage .agents/skills/test-coverage && 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 "test-coverage" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/test-coverage into .agents/skills/test-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-coverage", 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 scott-fryxell/brayness --skill test-coverage -a cursor

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

GitHub CLI

$ gh skill install scott-fryxell/brayness test-coverage --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/scott-fryxell/brayness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/test-coverage .cursor/skills/test-coverage && 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 "test-coverage" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/test-coverage into .cursor/skills/test-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-coverage", 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/scott-fryxell/brayness.git --path skills/test-coverage

--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 scott-fryxell/brayness --skill test-coverage -a gemini-cli

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

GitHub CLI

$ gh skill install scott-fryxell/brayness test-coverage --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/scott-fryxell/brayness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/test-coverage .gemini/skills/test-coverage && 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 "test-coverage" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/test-coverage into .gemini/skills/test-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-coverage", 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 scott-fryxell/brayness test-coverage

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 scott-fryxell/brayness --skill test-coverage -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/scott-fryxell/brayness.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/test-coverage .github/skills/test-coverage && 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 "test-coverage" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/test-coverage into .github/skills/test-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-coverage", 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 scott-fryxell/brayness --skill test-coverage -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 scott-fryxell/brayness test-coverage --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/scott-fryxell/brayness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/test-coverage .opencode/skills/test-coverage && 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 "test-coverage" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/test-coverage into .opencode/skills/test-coverage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "test-coverage", 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: test-coverage
GitHub stars: 125
Token cost: ~1.6k tokens
SKILL.md length: 450 words
Files: 6 (incl. scripts, references)
Skills in repo: 27
Repo updated: Sep 28, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Write Vitest specs for Vue 3 JavaScript (Vite Plus, happy-dom, @vue/test-utils) and analyze V8 coverage + Fallow health to prioritize test-first refactors.

Works in 7 steps: Risk report (start here) → Coverage-only table → HTML + line detail → …
Mocking composables
SKILL.md covers Stack, Commands, Writing specs and Coverage workflow, plus 4 more sections
Runs JavaScript scripts from its folder; calls npm, npx and node

What it does

Test Coverage is an agent skill from scott-fryxell/brayness. Write Vitest specs for Vue 3 JavaScript (Vite Plus, happy-dom, @vue/test-utils) and analyze V8 coverage + Fallow health to prioritize test-first refactors. Reference implementation is work/realness. Use when writing or fixing tests, mocking composables, improving coverage, or after test:coverage or npx fallow fails thresholds.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `references/fallow-integration.md`, `references/web-realness.md` and `scripts/lib/coverage-metrics.js`).

It sits in Testing & QA, covering Test coverage, Unit testing and Refactoring. It works with Vue.js, Vite, Vitest and JavaScript. The repository describes itself as: A harness for the anxious digital mind. A safe place for creatives to keep their creative soul while exploring digital skills. The licence is MIT.

When your agent uses it

Mocking composables
Improving coverage
After test:coverage
Npx fallow fails thresholds

Example prompts

“/test-coverage”

Requirements

Node.js

Workflow steps

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

Risk report (start here)
Coverage-only table
HTML + line detail
Fallow detail
Classify each item
Implement tests
Evolving Fallow config

What it can do on your machine

Read from SKILL.md and the folder at commit 71f10e2. 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
Ships 3 files in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
- npm
- npx
- node
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- vitest.dev
- test-utils.vuejs.org
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

Test Coverage loads about 1.6k tokens when it runs, and up to ~4.5k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 450 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~86
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~4.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 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); the scripts in this folder are not scanned.

SKILL.md

The full file from scott-fryxell/brayness at commit 71f10e2, republished under its MIT licence (© scott-fryxell). 450 words, ~1,605 tokens.

Download SKILL.mdSave it as .claude/skills/test-coverage/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.

name: test-coverage
description: Write Vitest specs for Vue 3 JavaScript (Vite Plus, happy-dom, @vue/test-utils) and analyze V8 coverage + Fallow health to prioritize test-first refactors. Reference implementation is work/realness. Use when writing or fixing tests, mocking composables, improving coverage, or after test:coverage or npx fallow fails thresholds.

Tests, coverage, and refactor risk

Canonical reference: work/realness (@realness.online/web). Run every command below from that directory.

Match tests/**/*.spec.js there. Do not introduce Jest, React Testing Library, TypeScript test files, or co-located *.test.ts.

Two jobs:

Write specs - patterns below; detail in references/web-realness.md
Prioritize - npm run test:risk before refactors; not a blind chase for 100%

Stack

Piece	What we use
Runner	Vite Plus - `vp test`, `import ... from 'vite-plus/test'`
Engine	Vitest (`vite-plus-test` alias)
DOM	`happy-dom`
Vue	`@vue/test-utils` - prefer `shallowMount`
Language	JavaScript + JSDoc
Coverage	V8, 80% global, `all: true`

Commands

bash

vp test run --reporter=dot          # npm run test
vp test watch                       # npm run test:watch
vp test run --coverage              # npm run test:coverage
vp test run --bail=1 --reporter=dot # npm run test:fail-fast
npm run test:risk                   # coverage + fallow + risk report

Pre-commit: vp check --fix && vp run type && vp test run.

Writing specs

Layout

All specs in tests/**/*.spec.js mirroring src/ (not co-located)
describe('@/utils/itemid', ...) or view/component name
@/ -> src/; @@/ -> tests/mocks/
Config: vite.config.js -> test block; setup: tests/setup.js, tests/mocks/

Skeleton

javascript

import { describe, it, expect, vi, beforeEach } from 'vite-plus/test'
import { fn_under_test } from '@/utils/example'

describe('@/utils/example', () => {
  beforeEach(() => {
    vi.clearAllMocks()
  })

  it('describes behavior in plain language', () => {
    expect(fn_under_test('input')).toBe('output')
  })
})

Test behavior, not internals (JS style: AGENTS.md).

Key patterns

Pattern	Approach	Reference spec
Pure utils	Input/output, nested `describe`	`tests/utils/itemid.spec.js`
Module mocks	Top-level `vi.mock()`; `vi.clearAllMocks()` in `beforeEach`	`tests/utils/itemid.spec.js`
Vue components	`shallowMount`, stubs, semantic queries	`tests/components/account/as-notifications.spec.js`
Composable mocks	`vi.hoisted()` refs for `vi.mock` closures	`tests/views/Account.spec.js`
Composables	`with_setup()` + `mount(defineComponent(...))`	`tests/use/poster.spec.js`
Async errors	`await expect(...).rejects.toThrow()`	`tests/utils/itemid.spec.js`

Hoisted mocks (reset .value in beforeEach):

javascript

const { mock_status, mock_enable } = vi.hoisted(() => {
  const create_ref = value => ({ value, __v_isRef: true })
  return {
    mock_status: create_ref('off'),
    mock_enable: vi.fn().mockResolvedValue(true)
  }
})

vi.mock('@/use/push', () => ({
  use_push: () => ({ status: mock_status, enable: mock_enable })
}))

Global mocks: tests/mocks/default.js, tests/mocks/browser/*. Per-spec mocks only when behavior differs.

mockReset: false in config - mocks keep implementations; clear call history each test.

What we do not do

Avoid	Use instead
Jest / React Testing Library	`vite-plus/test` + `@vue/test-utils`
TypeScript test files	`.spec.js` + JSDoc
`@faker-js/faker`	Domain fixtures (item IDs, directories)
supertest / live DB	Mock `idb-keyval`, `serverless`
`data-testid`	Semantic DOM queries
100% coverage	80% gate + risk report

Full patterns, templates, file map: references/web-realness.md

Coverage workflow

1. Risk report (start here)

bash

npm run test:risk
# or, if reports already exist:
npm run test:risk:report

Runs scripts/prioritize-refactor-risk.js.

Delete or wire - fallow unused-files; do not add tests
Test before refactor - ranked by coverage gap + CRAP + fan-in + hotspots + P0/P1

Options: --threshold 80 --top 25 --root .

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

2. Coverage-only table

bash

node skills/test-coverage/scripts/summarize-coverage.js --root .

3. HTML + line detail

Open coverage/index.html for uncovered lines.

4. Fallow detail

bash

npx fallow health --targets
npx fallow health --hotspots
npx fallow --format json

5. Classify each item

Verdict	Meaning
test-first	Add/extend specs before refactor
refactor-with-tests	Some coverage; shore up hot paths then refactor
delete-or-wire	Fallow unused file - entry point or delete
defer	Low product risk

Priority: P0 IDs/auth/sync/payments, P1 posters/potrace/3D, P2 rest.

6. Implement tests

Only when the user asks. Re-run npm run test:risk after changes.

7. Evolving Fallow config

When behavior changes, update .fallowrc.json, references/fallow-integration.md, and this file if needed.

Output format (risk reports)

markdown

# Refactor risk (coverage + fallow)

## Delete or wire
- ...

## Test before refactor
| file | pri | cov% | risk | ... |

## Workflow

Judgment principles

Unused in fallow graph -> delete or wire, not test
High complexity + low coverage + high fan-in -> test-first
Cycles (itemid <-> serverless, Directory) -> characterize with tests, then break
Nuclear triad: typecheck + lint + tests; coverage supports refactors
Match existing spec style; extend specs over new files
Excluded from coverage: src/main.js, src/router.js, src/wasm/**

Scripts

Script	Purpose
`scripts/summarize-coverage.js`	Coverage table
`scripts/prioritize-refactor-risk.js`	Coverage + fallow merge
`scripts/lib/coverage-metrics.js`	Shared Istanbul parsing

References

web-realness.md - stack, patterns, file map, judgment
fallow-integration.md - .fallowrc.json
Vitest: https://vitest.dev/
Vue Test Utils: https://test-utils.vuejs.org/

Files

SKILL.md and 5 other files (scripts, references) in skills/test-coverage of scott-fryxell/brayness.

SKILL.md
references/fallow-integration.md
references/web-realness.md
scripts/lib/coverage-metrics.js
scripts/prioritize-refactor-risk.js
scripts/summarize-coverage.js

Open the folder on GitHubat commit 71f10e2

Compare with similar skills

Test Coverage 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.

Test Coverage compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Test Coverage this skillscott-fryxell/brayness	125	—	~1.6k	Automated safety check: Pass	MIT	12 days ago
Vite Plusvictorgarciaesgi/regle	506	—	~303	Automated safety check: Pass	MIT	11 days ago
Vitest Skillsickn33/agentic-awesome-skills	47k	1 repos	~1.2k	Automated safety check: Pass	MIT	today
TDD Guidealirezarezvani/claude-skills	28k	—	~3.4k	Automated safety check: Pass	MIT	1 mo ago
TDD GuideLeoYeAI/openclaw-master-skills	2.2k	—	~1.4k	Automated safety check: Pass	MIT	2 mo ago
Browser Javascript TDDhashgraph-online/awesome-codex-plugins	1.3k	—	~797	Automated safety check: Pass	MIT	yesterday

Similar skills

Vite Plus
victorgarciaesgi/regle
Vite+ unified toolchain (vp CLI) usage for this project, wrapping Vite, Rolldown, Vitest, tsdown, Oxlint, Oxfmt, and Vite Task.
506 GitHub stars~303 tokensUpdated 11 days ago
Testing & QAAuto-check passed
Vitest Skill
sickn33/agentic-awesome-skills
Generates Vitest tests in JavaScript/TypeScript with Vite-native speed.
47k GitHub starsUsed in 1 repo~1.2k tokens
Testing & QAAuto-check passed
TDD Guide
alirezarezvani/claude-skills
Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and…
28k GitHub stars~3.4k tokensUpdated 1 mo ago
Testing & QAAuto-check passed
TDD Guide
LeoYeAI/openclaw-master-skills
Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and…
2.2k GitHub stars~1.4k tokensUpdated 2 mo ago
Testing & QAAuto-check passed
Browser Javascript TDD
hashgraph-online/awesome-codex-plugins
Test-drive browser JavaScript behavior with DOM fixtures, test runners, smoke tests, onload timing, selector refactors, and integration tradeoffs with Selenium or end-to-end tests.
1.3k GitHub stars~797 tokensUpdated yesterday
Testing & QAAuto-check passed
Testing
TheBeardedBearSAS/claude-craft
TDD/BDD testing principles. An agent skill from TheBeardedBearSAS/claude-craft.
107 GitHub stars~887 tokensUpdated 25 days ago
Testing & QAAuto-check passed

More from scott-fryxell/brayness

All 27 skills in this repo

Logo Finder
scott-fryxell/brayness
Find and install brand SVG logos via SVGL (https://svgl.app/) and Wikimedia Commons fallbacks into any project's static asset folder.
125 GitHub stars~1.1k tokensUpdated 12 days ago
Auto-check passed
Flexible Visual System
scott-fryxell/brayness
Derive a project's visual rules from its existing tokens, palette, type scale, logo, and icons (Intake), then generate raw SVG vector graphics from those rules as a small composable set (module…
125 GitHub stars~1.9k tokensUpdated 12 days ago
Auto-check passed
Hyperframes
scott-fryxell/brayness
Create video compositions, animations, title cards, overlays, captions, voiceovers, audio-reactive visuals, and scene transitions in HyperFrames HTML.
125 GitHub stars~3.2k tokensUpdated 12 days ago
Auto-check passed
Motion Systems
scott-fryxell/brayness
A skill your agent uses when designing or implementing motion for web interfaces, including CSS transitions and keyframes, linear() easing design, transform strategy (translate/rotate vs…
125 GitHub stars~1.7k tokensUpdated 12 days ago
Auto-check passed
Vue Inspect
scott-fryxell/brayness
Inspect live Vue 3 component state via agent-browser eval - no Devtools extension, no console.log.
125 GitHub stars~779 tokensUpdated 12 days ago
Auto-check passed
Vuetify To Semantic
scott-fryxell/brayness
Refactor a Vue page or component from Vuetify to semantic HTML5 + Schema.org microdata + Stylus element selectors.
125 GitHub stars~1.2k tokensUpdated 12 days ago
Auto-check passed

Works with

Questions about Test Coverage

What does Test Coverage do?

Write Vitest specs for Vue 3 JavaScript (Vite Plus, happy-dom, @vue/test-utils) and analyze V8 coverage + Fallow health to prioritize test-first refactors. Test Coverage is an agent skill from scott-fryxell/brayness. Write Vitest specs for Vue 3 JavaScript (Vite Plus, happy-dom, @vue/test-utils) and analyze V8 coverage + Fallow health to prioritize test-first refactors.

When should I use Test Coverage?

Test Coverage fits situations like: mocking composables; improving coverage; after test:coverage; npx fallow fails thresholds.

How do I install Test Coverage in Claude Code?

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

How do I install Test Coverage in Codex?

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

Can I use Test Coverage 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 scott-fryxell/brayness --skill test-coverage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-coverage, .gemini/skills/test-coverage, .github/skills/test-coverage and .opencode/skills/test-coverage in your project.

What does Test Coverage need to run?

Going by SKILL.md and its folder, Test Coverage needs JavaScript for the scripts in its folder and the command-line tools its instructions call (npm, npx and node). Our summary lists: Node.js.

Does Test Coverage access the network?

SKILL.md names 2 domains. As links in the text: vitest.dev and test-utils.vuejs.org. This is read from the text; nothing was executed.

Is Test Coverage 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Test Coverage use?

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

About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.9k tokens, read only when the agent opens those files.

What are the alternatives to Test Coverage?

Skills that share tags, products or a category with Test Coverage: Vite Plus (victorgarciaesgi/regle, 506 stars), Vitest Skill (sickn33/agentic-awesome-skills, 47k stars), TDD Guide (alirezarezvani/claude-skills, 28k stars) and TDD Guide (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Test Coverage?

scott-fryxell (a GitHub user) maintains it in scott-fryxell/brayness, which has 125 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on September 28, 2026.

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

Install Test Coverage

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

Tests, coverage, and refactor risk

Stack

Commands

Writing specs

Layout

Skeleton

Key patterns

What we do not do

Coverage workflow

1. Risk report (start here)

2. Coverage-only table

3. HTML + line detail

4. Fallow detail

5. Classify each item

6. Implement tests

7. Evolving Fallow config

Output format (risk reports)

Judgment principles

Scripts

References

Files

Compare with similar skills

Similar skills

More from scott-fryxell/brayness

Related

Questions about Test Coverage