doc-sync
Keeps IdeaVim documentation in sync with code changes. Use this skill when you need to verify documentation accuracy after code changes, or when checking if documentation (in doc/, README.md, CONTRIBUTING.md) matches the current codebase. The skill can work bidirectionally - from docs to code verification, or from code changes to documentation updates.
changelog
Maintains IdeaVim changelog (CHANGES.md) and build.gradle.kts changeNotes. Use when updating changelog, documenting releases, or reviewing commits/PRs for changelog entries.
tests-maintenance
Maintains IdeaVim test suite quality. Reviews disabled tests, ensures Neovim annotations are documented, and improves test readability. Use for periodic test maintenance.
issues-deduplication
Handles deduplication of YouTrack issues. Use when cleaning up duplicate issues, consolidating related bug reports, or organizing issue tracker.
extensions-api-migration
Migrates IdeaVim extensions from the old VimExtensionFacade API to the new @VimPlugin annotation-based API. Use when converting existing extensions to use the new API patterns.
teamcity-cli
Use when working with TeamCity CI/CD or when user provides a TeamCity build URL. Use `teamcity` CLI for builds, logs, jobs, queues, agents, and pipelines.
Enterprise Security
Central authority for Claude Code enterprise security. Covers enterprise managed policies (managed-settings.json), settings precedence hierarchy, policy file locations (macOS, Linux, Windows), unoverridable organizational policies, cloud execution security (isolated VMs, network access controls, credential protection), IDE security (VS Code, JetBrains), devcontainer security, and security best practices for teams. Assists with configuring enterprise policies, understanding precedence, and implementing organizational security standards. Delegates 100% to docs-management skill for official documentation.
mcp-jetbrains-ide
Control JetBrains IDE (IntelliJ, WebStorm, PyCharm) via MCP. Use when manipulating IDE files, running configurations, searching code, or performing refactoring. Triggers on "open in IDE", "run configuration", "refactor code", "IDE search", "JetBrains".
agent-client-protocol(ACP)
Agent Client Protocol (ACP) - Standardized communication between code editors and AI coding agents. Use for building ACP-compatible agents, integrating agents with editors (Zed, JetBrains, Neovim), implementing tool calls, file operations, and session management.
github-copilot
AI-powered coding assistant providing inline suggestions, chat interface, code review, and autonomous coding agent across IDEs and GitHub.com
plugin-deployment
Deploy IntelliJ IDEA plugins to the JetBrains Marketplace and remote servers. Used for publishing plugins, updating versions, deploying site documentation, and managing plugin releases. Supports version management, automated deployment workflows, and documentation generation.
jetbrains-vmoptions
Provides JetBrains IDE VM options knowledge for version-specific GC selection and memory/performance tuning (JDK 17/21, IDE 222+). Cross-platform only.
ide
Reference documentation for Claude Code IDE integrations — Desktop app (macOS/Windows), VS Code extension, JetBrains plugin, and Chrome browser extension. Covers installation, permission modes, session management, diff review, app preview, PR monitoring, connectors, plugins, SSH/remote sessions, keyboard shortcuts, extension settings, and troubleshooting.
IDE Documentation
Reference documentation for Claude Code IDE and desktop integrations — the Claude Desktop app (Code tab, permission modes, parallel sessions, diff view, preview servers, connectors, SSH/remote sessions, enterprise config), VS Code extension (installation, prompt box, @-mentions, plugin management, settings, CLI vs extension feature comparison), JetBrains plugin (supported IDEs, diff viewing, selection context, /ide command), and Chrome browser integration (automation, debugging, form filling, data extraction).
opening-in-rider
Opens a file or folder in JetBrains Rider using the nearest .sln or .csproj context when available. Use when the user asks to open code in Rider from the CLI.
GitHub Copilot
Use GitHub Copilot effectively for AI-assisted coding. Use when asked to: set up Copilot in VS Code or JetBrains, write custom Copilot instructions for a project, use chat slash commands, get better completions, use workspace agents, run Copilot in the terminal via gh CLI, configure Copilot for a team, or understand how Copilot uses context from your codebase.