youtrack
Manage YouTrack tickets for IdeaVim
Tracking VIM tickets is slow when you forget YouTrack commands. This skill gives clear command guidance for comments, tags, status, and releases.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "youtrack". Add a private comment to VIM-1234 asking Aleksei.Plate for clarification
Expected outcome:
- Use the add-comment command with the --private flag
- Target ticket VIM-1234
- Mention Aleksei.Plate in the comment text
Using "youtrack". Mark VIM-5678 as analyzed by Claude
Expected outcome:
- Use the add-tag command with tag ID 68-507461
- Run: npx tsx scripts-ts/src/youtrack-cli/add-tag.ts VIM-5678 68-507461
Using "youtrack". Set VIM-9999 fix version to 2.30.0
Expected outcome:
- Use the set-fix-version command
- Run: npx tsx scripts-ts/src/youtrack-cli/set-fix-version.ts VIM-9999 2.30.0
Security Audit
SafeAll 62 static findings are false positives. The scanner incorrectly flagged metadata fields (URLs, hashes) as security risks, documentation text as C2/cryptographic indicators, and code examples as shell execution. This directory contains only documentation (SKILL.md) that explains how to use external YouTrack CLI scripts. No executable code, network calls, or file operations exist in this skill folder.
Risk Factors
🌐 Network access (2)
📁 Filesystem access (1)
⚙️ External commands (50)
Quality Score
What You Can Build
Update ticket status
Move VIM tickets to Ready To Release after verification
Manage release versions
Create or delete YouTrack versions for IdeaVim releases
Post review comments
Add public or private comments requesting review on VIM tickets
Try These Prompts
Add a public comment to VIM-1234 that says the issue reproduces in 2.28.0
Add the claude-analyzed tag to VIM-1234 and confirm the tag ID used
Set the status of VIM-1234 to Ready To Release
Create a YouTrack version 2.29.0 and set VIM-1234 fix version to 2.29.0
Best Practices
- Confirm the VIM ticket key before running any command
- Use private comments for internal team requests only
- Reuse documented tag IDs to avoid mistakes and typos
Avoid
- Using GitHub Issues commands for IdeaVim YouTrack tickets
- Posting sensitive or personal details in public comments
- Setting ticket status without verifying the work is complete