agentsclimarketplace

Jira ops

Skill grandcamel/JIRA-Assistant-Skills/skills/jira-ops

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).From its SKILL.md

Install
npx -y skills add grandcamel/JIRA-Assistant-Skills --skill jira-ops

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

6.8 KB, as published. Nobody here has run it

JIRA Operations Skill

Cache management, request batching, and operational utilities for JIRA Assistant.

Risk Levels

OperationRiskNotes
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

When to Use This Skill

Use this skill when you need to:

  • Discover project context: Auto-discover project metadata, workflows, and usage patterns
  • Monitor cache status: Check cache size, entry counts, and hit rates
  • Clear cache data: Remove stale or sensitive cached data
  • Pre-warm cache: Load commonly accessed data for better performance
  • Optimize performance: Reduce API calls through effective caching
  • Troubleshoot slowness: Diagnose cache-related performance issues

What This Skill Does

IMPORTANT: Always use the jira-as CLI. Never run Python scripts directly.

  • Project Discovery: Discover project metadata and usage patterns (field fill rates, value distributions, parent hierarchy) for intelligent defaults
  • Cache Status Monitoring: Display cache statistics (size, entries, hit rates)
  • Cache Clearing: Remove cache entries by category, pattern, or all at once
  • Cache Warming: Pre-load project metadata and field definitions
  • Request Batching: Parallel request execution for bulk operations (programmatic API)

Quick Start

# Discover project context (prints to stdout)
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

Common Tasks (30-Second Solutions)

Check cache status

# 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

Warm the cache

# 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 cache

# 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 project context

# Discover and print project context to stdout (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

# Output goes to stdout only; redirect to save the full discovery data
jira-as ops discover-project PROJ -o json > project-context.json

Discovery output includes project metadata (issue types, components, versions, assignable users) plus pattern analysis of sampled issues: top assignees, common labels, per-field fill rates, value distributions (issue type, status, priority), and parent hierarchy usage. Use --output json to get the full discovery data.

See Commands Guide for complete documentation.

Available Commands

All commands support --help for full documentation.

CommandDescription
jira-as ops discover-projectDiscover project configuration and usage patterns (stdout only)
jira-as ops cache-statusDisplay cache statistics (size, entries, hit rate)
jira-as ops cache-clearClear cache entries (all, by category, or by pattern)
jira-as ops cache-warmPre-warm cache with commonly accessed data

Exit Codes

CodeMeaning
0Success
1Validation or general error
2Authentication error
3Permission denied
4Resource not found
5Rate limit exceeded
6Conflict error
7Server error
130Cancelled (Ctrl+C)

Configuration

Cache is stored in ~/.jira-skills/cache/ with configurable TTL per category.

See Configuration Guide for details.

Shared Libraries

This skill uses shared infrastructure from jira-as:

LibraryDescription
cache.pySQLite-based caching with TTL and LRU eviction
request_batcher.pyParallel request batching for bulk operations

See API Reference for programmatic usage.

Documentation

Keep looking

Skills are one crate of 628,853. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.