jira-scripts

Perform Jira ticket operations with lightweight bash scripts.

Updated Sep 8, 2025
One-click install
npx skills add https://github.com/randalmurphal/claude-config --skill jira-scripts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-scripts
Source: https://github.com/randalmurphal/claude-config/tree/main/project_specific_skills/jira-scripts
Command: npx skills add https://github.com/randalmurphal/claude-config --skill jira-scripts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill replaces heavy, token-expensive Jira MCP (Managed Code Package) functions with lightweight bash scripts, drastically reducing token usage and simplifying common Jira operations. It eliminates the complexity and overhead of traditional Jira integrations, making your AI workflows faster and more cost-effective.

Core Features & Use Cases

  • Comprehensive Jira Operations: Perform read (get issue), write (create, comment, update, log work, link tickets), and list (tickets, sprint) operations.
  • Massive Token Savings: Achieve 99.4% token savings (40k → 250 tokens) compared to Jira MCP.
  • Simplified Credential Management: Uses a single, gitignored credentials file (~/.claude/scripts/.jira-credentials).
  • Use Case: During a code review, automatically fetch all details for a linked Jira ticket, including description, acceptance criteria, and comments, to ensure full requirement coverage without leaving your AI environment.

Quick Start

Use the jira-scripts skill to fetch the complete details for Jira ticket INT-3877.

Frequently Asked Questions about jira-scripts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Jira ticket operations without heavy MCP tooling?

Automate Jira ticket operations using lightweight bash scripts that replace token-expensive MCP functions. This Skill provides dedicated scripts for reading, writing, and listing Jira issues, achieving 99.4% token savings compared to traditional Jira integration methods.

Can I fetch Jira ticket details and comments programmatically?

Yes, fetch complete Jira ticket details including description, acceptance criteria, and comments using the jira-get-issue script. This enables automated workflows that pull full requirement context without leaving your AI environment.

What Jira operations can I perform with bash scripts?

Perform comprehensive Jira operations: fetch issues, create tickets, add comments, update fields, log work, link tickets, list tickets, and view sprint details. Each operation uses a dedicated script with standardized exit codes and clear error messages.

How do I manage Jira credentials securely with automation scripts?

Store Jira credentials in a single gitignored file at ~/.claude/scripts/.jira-credentials. This centralized, per-user credential management simplifies setup while keeping sensitive data secure and separate from scripts.

Can I reduce token usage for Jira workflow automation?

Yes, bash scripts reduce token usage by 99.4% compared to Jira MCP—from 40k tokens down to 250 per operation. This drastically cuts costs while maintaining full functionality for ticket management, comments, and sprint operations.

Do I need special setup to use Jira automation scripts?

Minimal setup required: configure credentials in ~/.claude/scripts/.jira-credentials and use the provided scripts for read, write, and list operations. No heavy MCP dependencies or complex tooling needed.