CLAUDE.md

1# CLAUDE.md
2 
3Guidance for Claude Code when working with IdeaVim.
4 
5## Quick Reference
6 
7Essential commands:
8- `./gradlew runIde` - Start dev IntelliJ with IdeaVim
9- `./gradlew test -x :tests:property-tests:test -x :tests:long-running-tests:test` - Run standard tests
10 
11Avoid running all tests, this takes too long. It's preferred to run specific test.
12 
13When running gradle tasks, use `--console=plain` for cleaner output without progress bars.
14 
15See CONTRIBUTING.md for architecture details and a complete command list.
16 
17## IdeaVim-Specific Notes
18 
19- Property tests can be flaky - verify if failures relate to your changes
20- Use `<Action>` in mappings, not `:action`
21- Config file: `~/.ideavimrc` (XDG supported)
22- Goal: Match Vim functionality and architecture
23 
24## Issue Tracking
25 
26This project uses **YouTrack** for issue tracking, NOT GitHub Issues.
27- Tickets are prefixed with `VIM-` (e.g., VIM-1234)
28- YouTrack URL: https://youtrack.jetbrains.com/issues/VIM
29- `gh issue` commands will NOT work
30 
31## Commit Messages
32 
33For commits that fix a tracked issue, use the format `Fix(VIM-XXX): <description>` (e.g., `Fix(VIM-4115): NPE in CommandKeyConsumer after plugin disable/enable`).
34 
35## Additional Documentation
36 
37- Changelog maintenance: Handled by the `changelog` skill (auto-detected when updating changelog)
38 
39## Active Technologies
40- Kotlin (JVM 21) + IntelliJ Platform SDK, IdeaVim vim-engine (001-api-layer)
41 
42## Recent Changes
43- 001-api-layer: Added Kotlin (JVM 21) + IntelliJ Platform SDK, IdeaVim vim-engine
44