| name | YouTrack Integration |
| description | This skill should be used when the user mentions "YouTrack", "youtrack", asks about "tickets", "issues", "issue tracking", wants to "create a ticket", "change status", "update issue", "get issue info", "check issue", or needs to interact with their YouTrack instance. Provides knowledge about the YouTrack CLI and REST API patterns. |
YouTrack Integration
Use the YouTrack CLI to interact with the user's YouTrack instance.
CLI Usage
Run the CLI with npm:
npm run --prefix ${CLAUDE_PLUGIN_ROOT}/cli cli -- <command> [options]
Available Commands
Get Issue Details
npm run --prefix ${CLAUDE_PLUGIN_ROOT}/cli cli -- get <issue-id>
issue-id: The issue readable ID (e.g., "PROJ-123")
Returns JSON with: id, summary, description, project, state, type, priority, assignee.
Create Issue
npm run --prefix ${CLAUDE_PLUGIN_ROOT}/cli cli -- create <project-id> "<summary>" ["description"]
project-id: The project short name or ID (e.g., "PROJ", "DEV")summary: Issue title (quote if contains spaces)description: Optional issue description
Change Status
npm run --prefix ${CLAUDE_PLUGIN_ROOT}/cli cli -- status <issue-id> "<state-name>"
issue-id: The issue readable ID (e.g., "PROJ-123")state-name: Target state name (e.g., "In Progress", "Done", "Open")
Environment Variables
The CLI requires these environment variables (already configured in user's environment):
YOUTRACK_URL: YouTrack instance URLYOUTRACK_TOKEN: Permanent API token
Project Context
When the user doesn't specify a project:
- Check the conversation history for previously mentioned projects
- Look for project context in the codebase (e.g.,
.youtrackconfig, README mentions) - If unclear, ask the user which project to use
Never assume a default project - always confirm with the user if not explicitly provided.
State Names
Common YouTrack state names (may vary by project workflow):
- Open
- In Progress
- To be discussed
- Done
- Won't fix
- Duplicate
- Incomplete
If a state change fails, the error message will indicate available states.
Response Handling
The CLI outputs JSON on success. Parse the response to provide a clear summary to the user:
- For get: Display issue details in a readable format
- For create: Show the new issue ID and summary
- For status: Confirm the change was applied
Error Handling
If the CLI fails:
- Check if environment variables are set (error message will indicate)
- Verify the project/issue ID exists
- For status changes, verify the state name is valid for that project's workflow