Skip to content
Back to skills

Configure

ASecurity

View the resolved @vitest-agent/plugin configuration

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
testing

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add spencerbeggs/vitest-agent --skill configure --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Configure?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Configure
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/spencerbeggs-configure/badge)](https://www.skillsdirectory.com/skills/spencerbeggs-configure)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: configure
description: View the resolved @vitest-agent/plugin configuration
disable-model-invocation: true
---

# Configure @vitest-agent/plugin

Display the project's resolved `@vitest-agent/plugin` configuration. This
command is read-only — it parses the Vitest config and renders what is
set; it never mutates the file. To change a setting, edit
`vitest.config.ts` directly.

## 1. Locate the Vitest config

Look for `vitest.config.ts`, `vitest.config.js`, or `vitest.config.mjs`
at the project root. If none exists, stop and point the user at
`/vitest-agent:setup`.

## 2. Parse the `AgentPlugin({ ... })` call

Read the `AgentPlugin()` call from the `plugins` array. Extract the five
options fields: `console`, `coverageTargets`, `transport`, `reporter`,
and `onRunEvent`. Any field not present in the call is at its default.

## 3. Parse `test.coverage`

Read Vitest's native `test.coverage` block. Extract `enabled`,
`provider`, `thresholds`, and `watermarks`.

## 4. Render the two tables

Render the five-field options table and the Vitest coverage block, for
example:

```text
## vitest-agent options (AgentPlugin({ ... }))

| Field           | Value                                                |
| --------------- | ---------------------------------------------------- |
| console         | { human: "ink", agent: "agent", ci: "agent" }        |
| coverageTargets | AgentPlugin.COVERAGE_LEVELS.standard.coverageTargets |
| transport       | { kind: "local" } (default)                          |
| reporter        | (default — plugin built-in)                          |
| onRunEvent      | (default — no tee)                                   |

## Vitest coverage (test.coverage)

| Field      | Value                                           |
| ---------- | ----------------------------------------------- |
| enabled    | true                                            |
| provider   | "v8"                                            |
| thresholds | AgentPlugin.COVERAGE_LEVELS.standard.thresholds |
| watermarks | (default)                                       |
```

For any field left at its default, render `(default)` with a short note
of the default value rather than leaving the cell blank.

## 5. Detect the coverage preset

When `coverageTargets` and `thresholds` match one of the named presets
(`AgentPlugin.COVERAGE_LEVELS.{none|basic|standard|strict|full}`),
render the preset name. When they do not match a preset, render
`"custom"` and a per-metric breakdown of the actual values.

## 6. Point at the manual edit path

End by telling the user which file and line to edit for the
`AgentPlugin` options and for the Vitest coverage block, and point them
at the `configuration` skill for the field reference. Do not modify the
config.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.