tests-maintenance_skill

This skill maintains IdeaVim test quality by auditing disabled tests, documenting Neovim exclusions, and improving readability for safer, incremental
  • Kotlin

10.1k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill jetbrains/ideavim --skill tests-maintenance

  • SKILL.md10.4 KB

Overview

This skill maintains the IdeaVim test suite by reviewing disabled tests, ensuring Neovim exclusion annotations are documented, and improving test readability. It produces small, focused changes suitable for CI and PR review. Use it periodically to keep tests accurate and understandable without modifying production code.

How this skill works

It scans test sources for @Disabled, @TestWithoutNeovim, deprecated skip reasons, and meaningless test content. For a single selected test or method, it attempts to run the test (with and without Neovim when needed), re-enables passing tests, or updates annotations with specific reasons and descriptions. It also replaces placeholder text and improves test names or assertions to increase clarity.

When to use it

  • Periodic cleanup of test suite to reduce technical debt
  • After dependency or platform changes that may affect tests
  • When seeing many deprecated or undocumented TestWithoutNeovim annotations
  • Before a release to ensure tests are well-documented and runnable
  • When CI shows flaky or disabled tests that may be re-enabled

Best practices

  • Make one logical change per run: one test file or one test method only
  • If updating multiple annotations, group only when they share the exact same skip reason and fix
  • Always add a description parameter for non-obvious TestWithoutNeovim reasons
  • Prefer replacing vague reasons (DIFFERENT/UNCLEAR) with a specific category and evidence
  • Do not change production code or implement feature fixes in test-maintenance PRs

Example use cases

  • Re-enable a test that now passes after a platform bug was fixed and document why it was disabled
  • Add description to @TestWithoutNeovim(SCROLL) to explain viewport differences with Neovim
  • Replace meaningless Lorem-like strings with realistic code snippets to make assertions clearer
  • Split a test into two parts so only the Neovim-incompatible portion remains excluded
  • Change a deprecated skip reason to INTELLIJ_PLATFORM_INHERITED_DIFFERENCE with a short explanation

FAQ

One logical change per run: focus on a single test file or test method. Multiple edits are allowed only if they are identical annotation fixes across tests that share the same reason.

What evidence is required for IDEAVIM_WORKS_INTENTIONALLY_DIFFERENT?

Require explicit commit messages, code comments, or other corroborating documentation. Do not use this reason based on guesswork; include a clear description parameter.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational