Link Ticket To Session

Explicitly links your Claude Code session to a Linear, Jira, GitHub issue, or GitHub PR so karma can cache the title and status for display. You trigger it with commands like "/link-ticket-to-session ABC-123" or "attach this session to PR octocat/repo#7". It won't fire just because you mention a ticket in conversation. The implementation is careful about GitHub's shared numbering between issues and PRs, preserving the URL path so karma's UI knows which kind you meant. It fetches metadata through your existing MCP servers when available but gracefully skips that step if they're not configured. The link persists in karma's database and upgrades the source flag if you had previously linked via branch detection or the dashboard.

GitHub stars: 229
last updated: Jun 5, 2026

View on GitHub

Install

$ npx -y skills add jayantdevkar/claude-code-karma --skill link-ticket-to-session --agent claude-code

Installs into .claude/skills of the current project.

Files

You are linking the current Claude Code session (${CLAUDE_SESSION_ID}) to: $ARGUMENTS

Karma is a read-only observer on the user's machine. It stores the link and caches title/status for display, but never writes back to the ticket provider. You fetch metadata via the user's already-configured MCP server.

Karma's API URL comes from KARMA_API_URL (set by users on non-default ports/hosts) with http://localhost:8020 as fallback. Inline ${KARMA_API_URL:-http://localhost:8020} in every curl below — bash variables don't persist across separate Bash tool calls, so a top-of-script assignment would be empty by the time the next curl runs.