Debug Surefire
eclipse-rdf4j/rdf4j
Debug Maven Surefire unit tests by running them in JDWP "wait for debugger" mode (-Dmaven.surefire.debug) and attaching to the forked test JVM using jdb (preferred for CLI/agent debugging)…
Write IntelliJ JUnit 5 tests with fixtures, lifecycle, and EDT.
Install Writing Tests
$ npx skills add JetBrains/intellij-community --skill writing-tests -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JetBrains/intellij-community writing-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/JetBrains/intellij-community.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/writing-tests .claude/skills/writing-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 "writing-tests" agent skill from https://github.com/JetBrains/intellij-community/tree/master/.agents/skills/writing-tests into .claude/skills/writing-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-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/JetBrains/intellij-community/tree/master/.agents/skills/writing-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 JetBrains/intellij-community --skill writing-tests -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JetBrains/intellij-community writing-tests --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/intellij-community.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/writing-tests .agents/skills/writing-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 "writing-tests" agent skill from https://github.com/JetBrains/intellij-community/tree/master/.agents/skills/writing-tests into .agents/skills/writing-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-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 JetBrains/intellij-community --skill writing-tests -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JetBrains/intellij-community writing-tests --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/intellij-community.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/writing-tests .cursor/skills/writing-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 "writing-tests" agent skill from https://github.com/JetBrains/intellij-community/tree/master/.agents/skills/writing-tests into .cursor/skills/writing-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-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/JetBrains/intellij-community.git --path .agents/skills/writing-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 JetBrains/intellij-community --skill writing-tests -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JetBrains/intellij-community writing-tests --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/intellij-community.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/writing-tests .gemini/skills/writing-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 "writing-tests" agent skill from https://github.com/JetBrains/intellij-community/tree/master/.agents/skills/writing-tests into .gemini/skills/writing-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-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 JetBrains/intellij-community writing-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 JetBrains/intellij-community --skill writing-tests -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JetBrains/intellij-community.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/writing-tests .github/skills/writing-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 "writing-tests" agent skill from https://github.com/JetBrains/intellij-community/tree/master/.agents/skills/writing-tests into .github/skills/writing-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-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 JetBrains/intellij-community --skill writing-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 JetBrains/intellij-community writing-tests --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/intellij-community.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/writing-tests .opencode/skills/writing-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 "writing-tests" agent skill from https://github.com/JetBrains/intellij-community/tree/master/.agents/skills/writing-tests into .opencode/skills/writing-tests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-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
writing-tests- GitHub stars
- 21k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 605 words
- Files
- 1
- Skills in repo
- 39
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Write IntelliJ JUnit 5 tests with fixtures, lifecycle, and EDT.
- Testing & QA work in your project
- SKILL.md covers Place Tests in the Owning Module, Prefer JUnit 5 over JUnit 4, Shared Fixtures Pattern and Lifecycle Hooks, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Writing Tests is an agent skill from JetBrains/intellij-community, published by the product's own GitHub organization. Write IntelliJ JUnit 5 tests with fixtures, lifecycle, and EDT.
Its SKILL.md is about 1.7k 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. It works with JetBrains IDEs and JUnit. The repository describes itself as: IntelliJ IDEA & IntelliJ Platform.
When your agent uses it
- Testing & QA work in your project
Example prompts
- “/writing-tests”
What it can do on your machine
Read from SKILL.md and the folder at commit cbaf50b. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are kotlin and bash).
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
Writing Tests loads about 1.7k tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 605 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 605 words (~1,705 tokens).
“Guidelines for writing tests in IntelliJ IDEA codebase.”
- name
- writing-tests
Files
Just SKILL.md in .agents/skills/writing-tests of JetBrains/intellij-community.
Open the folder on GitHubat commit cbaf50b
Compare with similar skills
Writing 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 |
|---|---|---|---|---|---|---|
| Writing Tests this skillJetBrains/intellij-community | 21k | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Debug Surefireeclipse-rdf4j/rdf4j | 420 | — | ~2.4k | Automated safety check: Pass | BSD-3-Clause | |
| Mps TestsJetBrains/MPS | 1.7k | — | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Debug Playwright Prowquay/quay | 2.8k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Quay Prow Triagequay/quay | 2.8k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Swing Intellij Dialog Stylelakernote/easy-postman | 722 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Mps Tests
JetBrains/MPS
A skill your agent uses when writing or modifying tests inside MPS @tests models — NodesTestCase (typesystem, constraints, scopes, dataflow, generator output), EditorTestCase (intentions, actions…
Debug Playwright Prow
quay/quay
Deep-dive diagnosis of a Playwright test failure already isolated to one Quay Prow/OpenShift CI run: downloads its GCS artifacts (results.json, JUnit, build/pod logs, Jaeger traces), classifies real…
Quay Prow Triage
quay/quay
Diagnose any Quay Prow job failure end to end: prowjob.json - top-level build log - JUnit - resolved failing step - Playwright results.json when the failing step is Playwright, continuing through…
Swing Intellij Dialog Style
lakernote/easy-postman
A skill your agent uses when modifying EasyPostman Swing dialogs, popups, wizards, or modal flows to better match IntelliJ IDEA or FlatLaf settings-style visual hierarchy, especially when read-only…
Shopware CLI
shopware/shopware-cli
Use Shopware CLI for Shopware project, extension, and account workflows — create and install new projects (project create, project dev install), validate projects or extensions (with…
More from JetBrains/intellij-community
All 39 skills in this repo- Official
Youtrack Community
JetBrains/intellij-community
YouTrack CLI for a community checkout; the monorepo uses youtrack.
- Official
Compare Python Typecheckers
JetBrains/intellij-community
Compare Python type inference with ty, pyrefly, and basedpyright.
- Official
Sibling Checkout Commits
JetBrains/intellij-community
Take commits from a sibling checkout as patches, without a fetch.
- Official
Code Style
JetBrains/intellij-community
Apply IntelliJ Kotlin and Java code style when writing or reviewing.
- Official
Notebook For Experiment
JetBrains/intellij-community
Create reproducible Jupyter notebooks for performance experiments.
- Official
Jewel Markdown
JetBrains/intellij-community
Build or debug Jewel Markdown parsing, rendering, and styling.
Related
Works with
Categories
Questions about Writing Tests
What does Writing Tests do?
Write IntelliJ JUnit 5 tests with fixtures, lifecycle, and EDT. Writing Tests is an agent skill from JetBrains/intellij-community, published by the product's own GitHub organization. Write IntelliJ JUnit 5 tests with fixtures, lifecycle, and EDT.
When should I use Writing Tests?
Writing Tests fits situations like: testing & QA work in your project.
How do I install Writing Tests in Claude Code?
Run `npx skills add JetBrains/intellij-community --skill writing-tests -a claude-code`. Or copy the skill folder (.agents/skills/writing-tests in JetBrains/intellij-community) into .claude/skills/writing-tests in your project. Claude Code loads it when a task matches its description.
How do I install Writing Tests in Codex?
Run `npx skills add JetBrains/intellij-community --skill writing-tests -a codex`. Or copy the skill folder (.agents/skills/writing-tests in JetBrains/intellij-community) into .agents/skills/writing-tests in your project. Codex loads it when a task matches its description.
Can I use Writing 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 JetBrains/intellij-community --skill writing-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/writing-tests, .gemini/skills/writing-tests, .github/skills/writing-tests and .opencode/skills/writing-tests in your project.
What does Writing Tests need to run?
SKILL.md names no scripts, command-line tools or credentials: Writing Tests is instructions for the agent only.
Does Writing 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 Writing 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 Writing Tests use?
Writing Tests has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Writing Tests use?
About 1.7k tokens (SKILL.md is roughly 6.8k 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 Writing Tests?
Skills that share tags, products or a category with Writing Tests: Debug Surefire (eclipse-rdf4j/rdf4j, 420 stars), Mps Tests (JetBrains/MPS, 1.7k stars), Debug Playwright Prow (quay/quay, 2.8k stars) and Quay Prow Triage (quay/quay, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Tests?
JetBrains (a GitHub organization, an official publisher) maintains it in JetBrains/intellij-community, which has 20,617 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 9, 2026.
Source: JetBrains/intellij-community on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.