noob-ticket-cache

You can cache Jira and Confluence ticket context in one pass by fetching all relevant ticket data types simultaneously and storing them for downstream skills to reuse, avoiding individual API calls.

You can cache unified ticket context types including ticket_info, remote_links, comments, parent_issue, grandparent_issue, linked_tickets, and specific Confluence pages identified by pageId.

Run the ticket-context get command with your target ticket ID to load and cache all context types in one pass, preloading data before downstream skills execute to reduce latency.

Use the provided invalidate and purge commands when ticket data becomes stale or needs complete removal, utilizing TTL-managed cache to automatically handle expiration for Jira and Confluence context.

This approach works alongside Jira and Confluence MCP tools by enforcing a cache-first rule: it checks the cache before any MCP tool call, only fetching from MCP on a miss and saving immediately.