jira-ops_skill

Overview

This skill provides JIRA cache and performance operations to speed up API calls and discover project context. It exposes commands for cache status, warming, clearing, and project discovery, designed to run via the jira-as CLI. The skill focuses on read-only analysis and safe cache manipulation, with explicit flags for destructive actions.

How this skill works

The skill inspects local cache stored under ~/.jira-skills/cache and reports statistics such as size, entry counts, and hit rate. It can pre-fetch metadata (projects, fields, users) using request batching to reduce API round-trips and populate the cache. Cache-clear operations accept categories, patterns, and dry-run previews; cache-warm loads targeted datasets for faster subsequent requests.

When to use it

• When you need to discover project metadata, workflows, or usage patterns for automation defaults
• Before a high-volume operation to pre-warm common metadata and reduce API latency
• To check cache health: size, entry counts, and hit rate for troubleshooting slowness
• To remove stale or sensitive cached entries safely with dry-run and category filters
• When optimizing scripts or services that make repeated JIRA API calls to reduce rate limit pressure

Best practices

• Always run commands through the jira-as CLI; do not run Python scripts directly
• Use cache-status first to understand impact before clearing or warming the cache
• Prefer targeted cache-warm (projects, fields, users) instead of --all to limit API usage
• Use --dry-run and --pattern when clearing to avoid accidental data removal; require --force for destructive clears
• Monitor hit rate and TTL per category and tune TTLs in configuration for your workload

Example use cases

• Discover a project context to auto-populate workflow and field defaults for a new automation
• Warm field definitions and assignable users before running bulk processing to avoid repeated lookups
• Check cache hit rate and size after deploying a new integration to verify expected caching behavior
• Clear issue cache keys matching a pattern when imported data invalidates cached entries
• Pre-warm metadata for multiple projects before running a scheduled reporting job to minimize runtime API calls