E2E Test Thinker
UniClipboard/UniClipboard
Analyze the current branch's diff against main and determine which changes are testable via CLI-based end-to-end tests.
Author tests that match the repo's stack and existing test style, at the cheapest level that catches the regression.
Install Write Tests
$ npx skills add gnomeria/usbtree --skill write-tests -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gnomeria/usbtree write-tests --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/gnomeria/usbtree.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/write-tests .claude/skills/write-tests && rm -rf skills-srcUse ~/.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/
Install the "write-tests" agent skill from https://github.com/gnomeria/usbtree/tree/main/.agents/skills/write-tests into .claude/skills/write-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-tests", 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 install https://github.com/gnomeria/usbtree/tree/main/.agents/skills/write-testsType 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.
$ npx skills add gnomeria/usbtree --skill write-tests -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gnomeria/usbtree write-tests --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gnomeria/usbtree.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/write-tests .agents/skills/write-tests && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "write-tests" agent skill from https://github.com/gnomeria/usbtree/tree/main/.agents/skills/write-tests into .agents/skills/write-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-tests", 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.
$ npx skills add gnomeria/usbtree --skill write-tests -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gnomeria/usbtree write-tests --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gnomeria/usbtree.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/write-tests .cursor/skills/write-tests && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "write-tests" agent skill from https://github.com/gnomeria/usbtree/tree/main/.agents/skills/write-tests into .cursor/skills/write-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-tests", 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 https://github.com/gnomeria/usbtree.git --path .agents/skills/write-tests--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add gnomeria/usbtree --skill write-tests -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gnomeria/usbtree write-tests --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gnomeria/usbtree.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/write-tests .gemini/skills/write-tests && rm -rf skills-srcUse ~/.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/
Install the "write-tests" agent skill from https://github.com/gnomeria/usbtree/tree/main/.agents/skills/write-tests into .gemini/skills/write-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-tests", 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.
$ gh skill install gnomeria/usbtree write-testsInstalls 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).
$ npx skills add gnomeria/usbtree --skill write-tests -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gnomeria/usbtree.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/write-tests .github/skills/write-tests && rm -rf skills-srcUse ~/.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/
Install the "write-tests" agent skill from https://github.com/gnomeria/usbtree/tree/main/.agents/skills/write-tests into .github/skills/write-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-tests", 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.
$ npx skills add gnomeria/usbtree --skill write-tests -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gnomeria/usbtree write-tests --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gnomeria/usbtree.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/write-tests .opencode/skills/write-tests && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "write-tests" agent skill from https://github.com/gnomeria/usbtree/tree/main/.agents/skills/write-tests into .opencode/skills/write-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-tests", 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
write-tests- GitHub stars
- 688
- Token cost
- ~622 tokens
- SKILL.md length
- 299 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Author tests that match the repo's stack and existing test style, at the cheapest level that catches the regression.
- Works in 4 steps: Match repo style → Choose level → Write → …
- The user says write tests for
- SKILL.md covers Step 1 — Match repo style, Step 2 — Choose level, Step 3 — Write and Step 4 — Run and report
- Calls cargo
What it does
Write Tests is an agent skill from gnomeria/usbtree. Author tests that match the repo's stack and existing test style, at the cheapest level that catches the regression. Use when the user says "write tests for", "add test coverage", "test this function/handler/component", "this needs tests", or after implementing a feature that lacks tests.
Its SKILL.md is about 620 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Test generation and Test coverage. The repository describes itself as: Live USB device tree in your terminal. Rust TUI, no root, no libusb. Full activity metrics on Linux; device tree on macOS/Windows. The licence is MIT.
When your agent uses it
- The user says write tests for
- Add test coverage
- Test this function/handler/component
- This needs tests
Example prompts
- “write tests for”
- “add test coverage”
- “test this function/handler/component”
- “/write-tests”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 8ba6a5e. 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:
cargo
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
Write Tests loads about 622 tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 299 words of instructions outside code blocks.
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from gnomeria/usbtree at commit 8ba6a5e, republished under its MIT licence (© gnomeria). 299 words, ~622 tokens.
Download SKILL.mdSave it as
.claude/skills/write-tests/SKILL.md (or your agent's skills folder).- name
- write-tests
- description
- Author tests that match the repo's stack and existing test style, at the cheapest level that catches the regression. Use when the user says "write tests for", "add test coverage", "test this function/handler/component", "this needs tests", or after implementing a feature that lacks tests.
Write Tests
Test fails when behavior breaks, passes when it doesn't — nothing more. Run at end, report honestly.
Step 1 — Match repo style
- Tests live in-file:
#[cfg(test)] mod testsat bottom,use super::*. - Builder helpers for fat structs (see
dev()insrc/usb.rstests) — reuse existing helper, extend it, don't build parallel one. - Plain
assert_eq!/assert!. No assertion crates, no mock frameworks. - Raw descriptor bytes: inline arrays with
#[rustfmt::skip]+ comment per chunk (existing pattern).
Step 2 — Choose level
Cheapest level that catches the regression:
- Unit
#[test]— pure logic: tree flatten/fold, parsing (usb.ids, sysfs values, descriptors), diff. Default. No hardware, no I/O. - Smoke —
./target/release/usbtree --demo --dump: exercises scan→tree→render path, no hardware. For wiring bugs, not logic bugs. - TUI in pty —
--demoin pty for interaction (keys, fold, filter). Manual/scripted, last resort — most TUI logic is testable as pure functions on App state; prefer extracting that.
Pure parse bug tested through pty = wrong. Keybinding wiring tested as unit = also wrong. Match level to where bug lives.
Step 3 — Write
- Behavior, not implementation. Assert outputs and state, not internals.
- Name by behavior:
max_power_parses_sysfs,filter_finds_devices_in_collapsed_hubs— nottest1. - Independent tests: own data, no ordering deps. No shared mutable state — tests run parallel by default.
- Filesystem cases:
tempfile::TempDirif already a dep, else skip fs test and test the parse fn on a&strinstead — push I/O to edge, test the pure part. - Cover happy path, interesting failures (malformed input, missing sysfs file, truncated descriptor), boundary values. Skip permutations hitting same branch.
- Don't test nusb/ratatui — test your use of them.
Step 4 — Run and report
cargo test name_fragmentfirst, then fullcargo test.- Report pass/fail, verbatim output for red.
- Test caught real bug in code under test → fix code (or flag), never the test.
- Never weaken assertion or skip to get green. Never report green without running.
© gnomeria, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/write-tests of gnomeria/usbtree.
Open the folder on GitHubat commit 8ba6a5e
Compare with similar skills
Write Tests 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Write Tests this skillgnomeria/usbtree | 688 | — | ~622 | Automated safety check: Pass | MIT | |
| E2E Test ThinkerUniClipboard/UniClipboard | 1.8k | — | ~1.7k | Automated safety check: Pass | AGPL-3.0 | |
| Ralph Coveragejvm-skills/jvm-skills | 140 | — | ~683 | Automated safety check: Pass | Apache-2.0 | |
| Designing TestsCloudAI-X/opencode-workflow | 275 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Mutation Testingproffesor-for-testing/agentic-qe | 494 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Mutation Testjmagly/aiwg | 220 | — | ~3.2k | Automated safety check: Pass | MIT |
Similar skills
Ralph Coverage
jvm-skills/jvm-skills
Run Ralph in coverage mode — iteratively write tests for untested classes until coverage targets are met.
Designing Tests
CloudAI-X/opencode-workflow
Guides test strategy, TDD/BDD approaches, test coverage planning, and testing best practices.
Mutation Testing
proffesor-for-testing/agentic-qe
Test quality validation through mutation testing, assessing test suite effectiveness by introducing code mutations and measuring kill rate.
Mutation Test
jmagly/aiwg
Run mutation testing to validate test quality beyond code coverage.
Write Frontend Tests
Elite588/AUTOGPT
Analyze the current branch diff against dev, plan integration tests for changed frontend pages/components, and write them.
More from gnomeria/usbtree
Knowledge Graph
gnomeria/usbtree
Set up and maintain a lightweight, file-based knowledge graph of the repo — entities, typed relations, decisions, gotchas — so agents load context fast instead of re-exploring the codebase every…
CI GitHub Actions
gnomeria/usbtree
GitHub Actions CI pipeline conventions — job shape, caching, permissions, and action pinning.
Debug
gnomeria/usbtree
Systematic root-cause debugging — reproduce, isolate, fix at the source, prove the fix.
Refactor
gnomeria/usbtree
Behavior-preserving restructuring done safely — test net first, small verified steps, no mixed-in feature changes.
Related
Categories
Questions about Write Tests
What does Write Tests do?
Author tests that match the repo's stack and existing test style, at the cheapest level that catches the regression. Write Tests is an agent skill from gnomeria/usbtree. Author tests that match the repo's stack and existing test style, at the cheapest level that catches the regression.
When should I use Write Tests?
Write Tests fits situations like: the user says write tests for; add test coverage; test this function/handler/component; this needs tests.
How do I install Write Tests in Claude Code?
Run `npx skills add gnomeria/usbtree --skill write-tests -a claude-code`. Or copy the skill folder (.agents/skills/write-tests in gnomeria/usbtree) into .claude/skills/write-tests in your project. Claude Code loads it when a task matches its description.
How do I install Write Tests in Codex?
Run `npx skills add gnomeria/usbtree --skill write-tests -a codex`. Or copy the skill folder (.agents/skills/write-tests in gnomeria/usbtree) into .agents/skills/write-tests in your project. Codex loads it when a task matches its description.
Can I use Write Tests 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 gnomeria/usbtree --skill write-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-tests, .gemini/skills/write-tests, .github/skills/write-tests and .opencode/skills/write-tests in your project.
What does Write Tests need to run?
Going by SKILL.md and its folder, Write Tests needs the command-line tools its instructions call (cargo).
Does Write Tests access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Write Tests 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. Review the folder before installing.
What licence does Write Tests use?
Write Tests 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 Write Tests use?
About 622 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Write Tests?
Skills that share tags, products or a category with Write Tests: E2E Test Thinker (UniClipboard/UniClipboard, 1.8k stars), Ralph Coverage (jvm-skills/jvm-skills, 140 stars), Designing Tests (CloudAI-X/opencode-workflow, 275 stars) and Mutation Testing (proffesor-for-testing/agentic-qe, 494 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Write Tests?
gnomeria (a GitHub user) maintains it in gnomeria/usbtree, which has 688 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on August 20, 2026.
Source: gnomeria/usbtree on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.