Testing

What it does

When your agent uses it

• Testing changes
• Creating fixtures
• Running the test suite

Example prompts

• “write a test”
• “fix this bug”
• “add a fixture”
• “/testing”

Workflow steps

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

1. 1Reproduce — Run the failing scenario and observe the actual behavior
2. 2Write a failing test — Minimal reproduction as a test case
3. 3Commit the failing test — Use Skill(commit) with message like test: reproduce #issue-description
4. 4Fix the code — Only now attempt the fix
5. 5Verify — Run pnpm test and confirm the test passes
6. 6Commit the fix — Separate commit from the test

What it can do on your machine

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

  Shell commands in SKILL.md call:

  • pnpm
  • go

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

• Network

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

Testing loads about 649 tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 73 tokens; SKILL.md has 230 words of instructions outside code blocks.

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

~73

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

~649

With references · SKILL.md plus every file in references/, read only if the agent opens them

~1.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

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 poteto/noodle at commit 82d2921, republished under its MIT licence (© poteto). 230 words, ~649 tokens.

name

testing

description

Test-driven development workflow for Noodle. Use when testing changes, writing tests, fixing bugs, creating fixtures, or running the test suite. Triggers: "test", "write a test", "fix this bug", "add a fixture", "run tests", "TDD", or any task involving verification of code changes.

./scripts/scaffold-fixture.sh <package-dir> <fixture-name> [state-count]

pnpm fixtures:hash:sync

# Single package
go test ./loop

# Single test
go test ./loop -run TestLoopDirectoryFixtures

# Bypass cache
go test -count=1 ./parse

# With race detector
go test -race ./...

# Verbose
go test -v ./tui

if testing.Short() {
    t.Skip("skipping integration test in short mode")
}

© poteto, MIT. 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 1 other file (references) in .agents/skills/testing of poteto/noodle.

• SKILL.md
• references/fixtures.md

Open the folder on GitHubat commit 82d2921