# Maintain IdeaVim Tests with Focused Reviews

Disabled tests and unclear exclusions can hide regressions and weaken test quality. This skill reviews one focused area and produces documented, reviewable maintenance changes.

## Install

```bash
npx skillstore add jetbrains/tests-maintenance
```

## Metadata

- Status: approved
- Slug: jetbrains-tests-maintenance
- Skillstore revision: r2
- Version status: missing
- Tree hash: 1c8c65da07d742d5f93cfdb4ecee37eaba06c5c0d7fdefc2b511839cbcbdc5de
- Author: JetBrains
- GitHub username: JetBrains
- License: MIT
- Repository: https://github.com/JetBrains/ideavim/tree/master/.claude/skills/tests-maintenance
- Ref: ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/jetbrains-tests-maintenance
- Manifest: https://skillstore.pages.dev/api/skills/jetbrains-tests-maintenance/manifest

## Capabilities

- Selects one IdeaVim test file or method for a focused maintenance run.
- Finds disabled Kotlin tests and checks whether targeted Gradle tests now pass.
- Reviews TestWithoutNeovim reasons and requires descriptions for non-obvious exclusions.
- Runs targeted or standard Gradle tests, including optional Neovim verification.
- Replaces meaningless test content with realistic examples and improves test names.
- Prepares a focused pull request title and body describing the review and changes.

## Use Cases

- Recheck Disabled Tests: Run one disabled test, investigate its history, and re-enable it only when the result is stable and explained.
- Document Neovim Exclusions: Replace vague exclusion reasons with specific categories and descriptions supported by test results or repository evidence.
- Improve Test Readability: Replace meaningless fixture text and clarify test names while preserving the tested behavior.

## Prompt Templates

### Review One Disabled Test

```
Find one disabled IdeaVim test, run it, and report whether it can be re-enabled. Explain the evidence and keep changes limited to that test.
```

### Check One Neovim Exclusion

```
Review one TestWithoutNeovim annotation. Verify the reason, run the test with Neovim when possible, and add a specific description if needed.
```

### Improve One Test File

```
Inspect one IdeaVim test file for unclear names or meaningless content. Make one logical readability improvement without changing production behavior.
```

### Investigate Deprecated Exclusions

```
Choose one DIFFERENT or UNCLEAR exclusion. Test with Neovim, inspect relevant history, classify the cause, and prepare a focused pull request summary.
```

## Limitations

- The workflow is tailored to the IdeaVim repository structure, annotations, and Gradle tasks.
- Test execution requires the repository dependencies and any configured Neovim test environment.
- The skill does not fix production bugs, implement features, or perform major refactoring.
- Passing tests do not prove that an exclusion is obsolete without reviewing history and behavior.

## Best Practices

- Keep each run and pull request limited to one logical test maintenance change.
- Verify Neovim mode is active before drawing conclusions from compatibility test results.
- Use test output, history, comments, or platform documentation to justify exclusion reasons.

## Anti Patterns

- Do not combine unrelated annotation, content, and disabled-test changes in one pull request.
- Do not classify intentional behavior differences from assumptions without supporting evidence.
- Do not expand maintenance work into production fixes, new features, or major refactoring.

## Security Audit

- Audited at: 2026-07-23T15:36:46.127\+00:00
- Summary: All 76 static findings are false positives caused by Markdown backticks, documented local test commands, or ordinary review wording. The skill contains no prompt injection, exfiltration intent, covert network access, or unsafe command construction.

## Stats

- Views: 212
- Downloads: 8
- Favorites: 0
- Popularity score: 0