skills/jira-ops/SKILL.md
JIRA cache and performance operations. TRIGGERS: 'warm the cache', 'warm cache', 'cache status', 'clear cache', 'cache warm', 'cache for project', 'discover project', 'project discovery', 'cache hit rate', 'optimize performance', 'rate limit'. Use for JIRA API performance optimization and project context discovery. NOT FOR: project configuration/settings (use jira-admin), issue operations (use jira-issue), bulk issue modifications (use jira-bulk).
npx skillsauth add grandcamel/jira-assistant-skills jira-operationsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Cache management, request batching, and operational utilities for JIRA Assistant.
| Operation | Risk | Notes |
|-----------|------|-------|
| Discover project | - | Read-only analysis |
| Cache status | - | Read-only |
| Cache warm | - | Populates local cache |
| Cache clear (dry-run) | - | Preview only |
| Cache clear | ! | Local cache cleared, will re-fetch |
Risk Legend: - Safe, read-only | ! Caution, modifiable | !! Warning, destructive but recoverable | !!! Danger, irreversible
Use this skill when you need to:
IMPORTANT: Always use the jira-as CLI. Never run Python scripts directly.
# Discover project context (saves to skill directory by default)
jira-as ops discover-project PROJ
# Check cache status
jira-as ops cache-status
# Clear all cache
jira-as ops cache-clear --force
# Warm cache with all metadata
jira-as ops cache-warm --all
# Basic status
jira-as ops cache-status
# Output as JSON
jira-as ops cache-status --json
# Verbose output (-v is short for --verbose)
jira-as ops cache-status -v
jira-as ops cache-status --verbose
# Cache project list
jira-as ops cache-warm --projects
# Cache field definitions
jira-as ops cache-warm --fields
# Cache assignable users (requires project context)
jira-as ops cache-warm --users
# Cache all available metadata with verbose output
jira-as ops cache-warm --all --verbose
# Output as JSON
jira-as ops cache-warm --all --json
# Clear all cache (with confirmation)
jira-as ops cache-clear
# Clear all cache (skip confirmation, -f is short for --force)
jira-as ops cache-clear -f
jira-as ops cache-clear --force
# Clear only issue cache (-c is short for --category)
# Categories: issue, project, user, field, search, default
jira-as ops cache-clear -c issue -f
jira-as ops cache-clear --category issue --force
# Preview what would be cleared
jira-as ops cache-clear --dry-run
# Clear keys matching pattern
jira-as ops cache-clear --pattern "PROJ-*" -c issue -f
# Clear specific cache key (requires --category)
jira-as ops cache-clear --key "PROJ-123" -c issue -f
# Output as JSON
jira-as ops cache-clear -f --json
# Discover and output project context (text format)
jira-as ops discover-project PROJ
# Output as JSON (-o is short for --output)
jira-as ops discover-project PROJ -o json
jira-as ops discover-project PROJ --output json
# Verbose output with detailed analysis (-v is short for --verbose)
jira-as ops discover-project PROJ -v
# Custom sample size and period (-s, -d are short forms)
jira-as ops discover-project PROJ -s 200 -d 60
jira-as ops discover-project PROJ --sample-size 200 --days 60
See Commands Guide for complete documentation.
All commands support --help for full documentation.
| Command | Description |
|---------|-------------|
| jira-as ops discover-project | Discover project metadata, workflows, and patterns |
| jira-as ops cache-status | Display cache statistics (size, entries, hit rate) |
| jira-as ops cache-clear | Clear cache entries (all, by category, or by pattern) |
| jira-as ops cache-warm | Pre-warm cache with commonly accessed data |
| Code | Meaning | |------|---------| | 0 | Success | | 1 | General error | | 2 | Configuration error | | 3 | Cache database error | | 4 | Network error |
Cache is stored in ~/.jira-skills/cache/ with configurable TTL per category.
See Configuration Guide for details.
This skill uses shared infrastructure from jira-as:
| Library | Description |
|---------|-------------|
| cache.py | SQLite-based caching with TTL and LRU eviction |
| request_batcher.py | Parallel request batching for bulk operations |
See API Reference for programmatic usage.
data-ai
Time tracking, worklogs, and time reports. TRIGGERS: 'log time', 'time spent on', 'log hours', 'log work', 'worklog', 'time tracking', 'timesheet', 'how much time', 'time logged', 'time report', 'export timesheet', 'set estimate', 'remaining estimate', 'original estimate'. Use for time-related queries and operations on issues. NOT FOR: SLA tracking (use jira-jsm), date-based issue searches (use jira-search), issue field updates unrelated to time (use jira-issue).
tools
Find issues by criteria (status, assignee, priority, etc.) using JQL. Create filters, export results to CSV/JSON, bulk update. Ideal for reporting and automation.
testing
Issue linking, blockers, and dependency analysis. TRIGGERS: 'what's blocking', 'what is blocking', 'is blocked by', 'link issues', 'link to', 'blockers for', 'depends on', 'clone issue', 'clone with', 'blocking chain', 'dependency graph', 'show dependencies', 'get blockers', 'relates to', 'duplicates'. Use for issue dependencies, relationships, and cloning. NOT FOR: epic linking (use jira-agile), field updates (use jira-issue), bulk cloning (use jira-bulk).
tools
Manage issue lifecycle through workflow transitions and status changes. Control who does what and when via assignments, versions, and components.