Assessing Test Coverage

What it does

When your agent uses it

• Determining what test coverage ALREADY exists for a specific change (a PR
• Tech Breakdown doc
• Named component)
• Whats already tested

Example prompts

• “s already tested”
• “does this PR have tests”
• “what coverage exists for”
• “/assessing-test-coverage”

Requirements

• Pre-approved tools (allowed-tools): Read, Write, Grep, Glob, Bash(date:*), Bash(gh pr view:*), Bash(gh pr diff:*), Bash(gh api repos/bitwarden/*), Bash(gh search code:*), Bash(git rev-parse:*), Bash(git remote get-url:*), Bash(git -C * rev-parse:*), Bash(git -C * remote get-url:*), Bash(git clone:*), Skill(bitwarden-atlassian-tools:researching-jira-issues)

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

1. 1Resolve the input into a change surface (changed paths/symbols, named components) and the repos it touches
2. 2List the change's testable behaviors.
3. 3For each behavior, find the tests covering it: tests in the linked PR diffs first, then a lookup scoped to the change surface. Include E2E.
4. 4Record each behavior: layer (unit / integration / E2E), representative test permalink(s), count, source. Behaviors with no test found →…
5. 5Write the report to ${CLAUDE_PLUGIN_DATA}/coverage-reports/--coverage.md ( from the ticket/PR/feature; from date +%Y-%m-%d-%H%M%S) using…

What it can do on your machine

Read from SKILL.md and the folder at commit 0047fdf. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Read
  • Write
  • Grep
  • Glob
  • Bash(date:*)
  • Bash(gh pr view:*)
  • Bash(gh pr diff:*)
  • Bash(gh api repos/bitwarden/*)
  • Bash(gh search code:*)
  • Bash(git rev-parse:*)

  …and 5 more on the same allowed-tools line.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • gh

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

• Network

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

Assessing Test Coverage loads about 1.1k tokens when it runs. Until then it costs about 183 tokens; SKILL.md has 318 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~183

When it runs · the whole SKILL.md, loaded when a task matches

~1.1k

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

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 318 words (~1,074 tokens).

name

assessing-test-coverage

allowed-tools

Read, Write, Grep, Glob, Bash(date:*), Bash(gh pr view:*), Bash(gh pr diff:*), Bash(gh api repos/bitwarden/*), Bash(gh search code:*), Bash(git rev-parse:*), Bash(git remote get-url:*), Bash(git -C * rev-parse:*), Bash(git -C * remote get-url:*), Bash(git clone:*), Skill(bitwarden-atlassian-tools:researching-jira-issues)

argument-hint

[PR URL | Jira key | Tech Breakdown doc | Testmo CSV]

Read the full SKILL.md on GitHub

Files

SKILL.md and 2 other files in plugins/bitwarden-testing-tools/skills/assessing-test-coverage of bitwarden/ai-plugins.

• SKILL.md
• evals/baseline.json
• evals/trigger-eval.json

Open the folder on GitHubat commit 0047fdf