Recommending Test Layers

What it does

When your agent uses it

• Deciding WHICH new tests a change needs and at WHICH layer each belongs
• Working from a Jira key
• An assessing-test-coverage report
• A feature description

Example prompts

• “should I add integration tests here”
• “are unit tests enough”
• “what tests should I add and where”
• “/recommending-test-layers”

Requirements

• Pre-approved tools (allowed-tools): Read, Write, Grep, Glob, Bash(date:*), Bash(gh pr view:*), Bash(gh pr diff:*), Skill(bitwarden-atlassian-tools:researching-jira-issues), mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_confluence_page

Workflow steps

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

1. 1Resolve the input into a set of testable behaviors and the repos they touch
2. 2Establish what is already tested so recommendations target gaps. Prefer an assessing-test-coverage report as input; if none is supplied…
3. 3For each behavior, assign the deterministic layer that earns confidence at the narrowest sufficient scope.
4. 4Decide which behaviors additionally earn a non-deterministic layer on top of their step-3 coverage. Add one only when its trigger is met…
5. 5When the input shows where tests already live — an assessing-test-coverage report or a PR diff — flag any behavior mis-placed (an edge…
6. 6Write the report to ${CLAUDE_PLUGIN_DATA}/recommending-test-layers/--test-layers.md ( from the ticket, PR, or feature; from date…

What it can do on your machine

Read from SKILL.md and the folder at commit 53e22a3. 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:*)
  • Skill(bitwarden-atlassian-tools:researching-jira-issues)
  • mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_confluence_page

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

  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

Recommending Test Layers loads about 2.4k tokens when it runs. Until then it costs about 228 tokens; SKILL.md has 788 words of instructions outside code blocks.

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

~228

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

~2.4k

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 788 words (~2,432 tokens).

name

recommending-test-layers

allowed-tools

Read, Write, Grep, Glob, Bash(date:*), Bash(gh pr view:*), Bash(gh pr diff:*), Skill(bitwarden-atlassian-tools:researching-jira-issues), mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_confluence_page

argument-hint

[Jira key | Testmo CSV | assessing-test-coverage report | PR URL | feature description]

Read the full SKILL.md on GitHub

Files

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

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

Open the folder on GitHubat commit 53e22a3