Audit disabled IdeaVim tests and document Neovim annotations.
npx skills add https://github.com/JetBrains/ideavim --skill tests-maintenance
Please help me install this Agent Skill. Skill: tests-maintenance Source: https://github.com/JetBrains/ideavim/tree/main/.claude/skills/tests-maintenance Command: npx skills add https://github.com/JetBrains/ideavim --skill tests-maintenance
Maintains IdeaVim test suite quality by auditing disabled tests, documenting Neovim annotations, and improving test readability and consistency across the suite.
Review a small subset of tests and update a single disabled case with an explicit description and rationale.
High-intent search queries and answers about installing and using this skill.
Auditing disabled IdeaVim tests involves reviewing each skipped case for potential re-enablement and documenting clear justification for why it remains excluded. This ensures test suite health by providing explicit rationale for any disabled test logic.
Documenting Neovim annotations requires adding explicit exclusion reasons and expected behavior differences for each skipped IdeaVim test case. This documentation clarifies why specific Neovim behaviors are excluded and what the expected differences are.
Improving IdeaVim test readability involves updating test content, naming, and structure to enforce code-quality standards. Restructuring tests into small, well-scoped changes reduces flakiness and speeds up the review process.
IdeaVim test maintenance applies changes through small, well-scoped PRs that integrate with standard CI workflows. It enforces code-quality standards for test content and documentation without requiring specialized CI environment configuration beyond standard Neovim and IdeaVim setups.
Excluding specific IdeaVim tests is necessary when documenting Neovim behavior differences or addressing flaky tests that cannot be immediately resolved. The maintenance process requires providing a clear rationale and explicit description for any test that remains disabled.
jmaglyAnalyze CI history and test execution patterns to identify flaky tests.
mkalkereIdentify and fix code smells through behavior-preserving refactoring with test verification.
Sheldon-92Execute test suites and report failures with coverage metrics.
gujiachun-rainbowReplace arbitrary delays with configurable condition polling in test suites.
