Atlas / Skills / dicklesworthstone / Jira

JiraCAUTION

skills/dicklesworthstone/jira

High-performance AI coding agent CLI written in Rust with zero unsafe code

Verdict
CAUTION
Grade
B
Trust score
89 /100
Version
—
Hosts
—
License
NOASSERTION
Stars
1,872
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

Browse and manage Jira issues using the jira-cli tool.

Overview

This skill enables interacting with Jira from the command line. You can:

  • List, view, create, and edit issues
  • Transition issues between statuses
  • Manage comments and worklogs
  • Work with epics and sprints
  • Search using JQL

Installation

  1. Install jira-cli:
brew install jira-cli
  1. Get API token: https://id.atlassian.com/manage-profile/security/api-tokens
  1. Configure:
export JIRA_API_TOKEN="your-token"
jira init

Quick Start

# List your assigned issues
jira issue list --assignee "$(jira me)"

# View an issue
jira issue view ISSUE-123

# Create an issue
jira issue create "Fix the bug"

# Start working on an issue
jira issue transition ISSUE-123 "In Progress"

# Mark as done
jira issue transition ISSUE-123 "Done"

See Also

Read from source at commit 46a2537504c9OBSERVED · 2026-10-10
02

What it tells the agent

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: jira
description: Interact with Jira using the jira-cli tool. Search, create, view, edit, and transition issues; manage epics and sprints; add comments and worklogs. Use when working with Jira tickets, backlogs, or project management tasks.
---

# Jira Skill

Interactive Jira command line tool for managing issues, epics, sprints, and more.

## Setup

### Installation

Install `jira-cli`:

```bash
# macOS (Homebrew)
brew install jira-cli

# Or download from releases
# https://github.com/ankitpokhrel/jira-cli/releases
```

### Configuration

1. Get a Jira API token for Jira Cloud: https://id.atlassian.com/manage-profile/security/api-tokens
2. Export the token:

```bash
export JIRA_API_TOKEN="your-api-token"
```

Add to your shell config (`~/.bashrc`, `~/.zshrc`, etc.) to make it persistent.

3. Initialize jira-cli:

```bash
jira init
```

Follow the prompts to configure:
- Installation type (Cloud or Local)
- Base URL (e.g., `https://yourcompany.atlassian.net`)
- Email/username
- Project key (optional, can be set per command)

For on-premise installations, you may need to set:

```bash
export JIRA_AUTH_TYPE="bearer"  # or "basic"
```

## List Issues

```bash
# List recent issues (interactive)
jira issue list

# List issues created in last 7 days
jira issue list --created -7d

# List issues by status
jira issue list -s "To Do"
jira issue list -s "In Progress"
jira issue list -s "Done"

# List issues by priority
jira issue list --priority High

# List issues by assignee
jira issue list --assignee $(jira me)

# List issues by reporter
jira issue list --reporter $(jira me)

# List issues by label
jira issue list --label backend

# List issues by project
jira issue list --project PROJKEY

# Plain output (non-interactive)
jira issue list --plain

# JSON output (for parsing)
jira issue list --raw

# CSV output
jira issue list --csv

# Complex query: High priority, assigned to me, in To Do, created this month
jira issue list --priority High --assignee $(jira me) -s "To Do" --created month --label backend
```

### Common Filters

| Flag | Description | Example |
|------|-------------|---------|
| `-s, --status` | Filter by status | `-s "In Progress"` |
| `-y, --priority` | Filter by priority | `--priority High` |
| `-l, --label` | Filter by label | `-l backend` |
| `-a, --assignee` | Filter by assignee | `-a $(jira me)` |
| `-r, --reporter` | Filter by reporter | `-r $(jira me)` |
| `--created` | Filter by creation date | `--created -7d`, `--created month` |
| `--updated` | Filter by update date | `--updated -7d` |
| `-p, --project` | Filter by project | `-p PROJKEY` |
| `--type` | Filter by issue type | `--type Bug` |

## View Issues

```bash
# View issue details in terminal
jira issue view ISSUE-123

# View without pager
jira issue view ISSUE-123 --no-pager

# View in browser
jira issue view ISSUE-123 --web
```

## Create Issues

```bash
# Interactive creation (prompts for all fields)
jira issue create

# Create with summary only
jira issue create "Fix login bug"

# Create with type and summary
jira issue create --type Bug "Fix login bug"

# Create with all fields
jira issue create \
  --type Bug \
  --summary "Fix login bug" \
  --description "Users cannot login after update" \
  --priority High \
  --assignee "$(jira me)" \
  --label backend,auth \
  --project PROJKEY
```

## Edit Issues

```bash
# Interactive edit (opens in editor)
jira issue edit ISSUE-123

# Edit summary
jira issue edit ISSUE-123 --summary "New summary"

# Edit description
jira issue edit ISSUE-123 --description "Updated description"

# Edit priority
jira issue edit ISSUE-123 --priority High

# Change assignee
jira issue edit ISSUE-123 --assignee "$(jira me)"

# Add labels
jira issue edit ISSUE-123 --label backend,bug
```

## Transition Issues

```bash
# Interactive transition (choose from available transitions)
jira issue transition ISSUE-123

# Transition to specific status
jira issue transition ISSUE-123 "In Progress"
jira issue transition ISSUE-123 "Done"
jira issue transition ISSUE-123 "In Review"
```

## Comments

```bash
# Add comment
jira issue comment add ISSUE-123 "This needs more testing"

# Add comment with markdown
jira issue comment add ISSUE-123 "**Note:** This is a priority issue."

# List comments
jira issue comment list ISSUE-123

# Edit comment
jira issue comment edit ISSUE-123 "Comment ID" "Updated comment"

# Delete comment
jira issue comment delete ISSUE-123 "Comment ID"
```

## Worklog (Time Tracking)

```bash
# Add worklog
jira issue worklog add ISSUE-123 --time "2h" --message "Fixed the bug"

# Add worklog with specific time
jira issue worklog add ISSUE-123 --time "1d 2h 30m" --message "Implementation"

# List worklogs
jira issue worklog list ISSUE-123

# Delete worklog
jira issue worklog delete ISSUE-123 "Worklog ID"
```

## Epics

```bash
# List epics
jira epic list

# List epics in plain mode
jira epic list --plain

# Create epic
jira epic create \
  --name "Authentication System" \
  --summary "Implement OAuth2 authentication" \
  --description "Add OAuth2 login flow"

# View epic details
jira epic view EPIC-123

# List issues in epic
jira epic list EPIC-123

# Add issues to epic
jira issue edit ISSUE-123 --epic EPIC-123
```

## Sprints

```bash
# List sprints
jira sprint list

# List active sprint issues
jira sprint list --state active

# List issues in sprint
jira sprint list SPRINT-123

# Start sprint
jira sprint start SPRINT-123

# Close sprint
jira sprint close SPRINT-123
```

## Projects

```bash
# List projects
jira project list

# View project details
jira project view PROJKEY
```

## Current User

```bash
# Get current user info
jira me

# Get current user key
jira me --key

# Use in other commands
jira issue list --assignee "$(jira me)"
```

## Search (JQL)

```bash
# Jira Query Language (JQL) search
jira issue list --query "project = PROJKEY AND status = 'In Progress'"

# Complex JQL
jira issue list --query 'project = PROJKEY AND assignee = currentUser() AND priority = High'
03

Trust audit

CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.

LayerWhat it checksResult
L0Provenance & inventoryWARN
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)FAIL
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
pinned
Secrets in source
none-found

Findings (2)

HIGHPrompt injection · prompt.persistence · CWE-94, CWE-1427
SKILL.md:33
Add to your shell config (`~/.bashrc`, `~/.zshrc`, etc.) to make it persistent.
Why it matters. instructs the agent to persist itself in the user's environment
MEDIUMInventory / provenance · inv.symlink · CWE-1104
.beads/beads.jsonl
.beads/beads.jsonl
Why it matters. link not followed

Gates applied: no_behavioural_pass.

Audited 2026-10-10 · audit v0.4.1 · source sha 46a2537504c9full audit observations/trust-audit/skill/dicklesworthstone__jira.json · Report an issue / request a re-scan
04

Audit history

Every audit this skill has had.

DateSourceVerdictGradeScoreChange
2026-10-1046a2537504c9CAUTIONB89first audit
05

Questions

What does the Jira skill do?

High-performance AI coding agent CLI written in Rust with zero unsafe code

Is Jira safe to install?

With care. The audit graded it B (89/100) and found 2 things worth knowing before you trust this skill, listed below with the exact line each was found on.

What can Jira access on my machine?

The audit observed no filesystem, network or shell use at all in its source.

What do I need installed to use Jira?

Its own instructions reference jira-cli. Dependencies are pinned to exact versions.

How current is this page?

The grade is for one exact copy of the source (46a2537504c9), read on 2026-10-10. The repository is watched, and a new audit runs when it changes — this is the first audit.

Advertisement