jirac

Jira issue management skill for OpenClaw using the jirac CLI. Requires the `jirac` binary to be installed and authenticated before use. Use when listing, vie...

Security Scan

The skill is an instruction-only wrapper around the jirac CLI and its requirements and guidance are consistent with that purpose.

Purpose & Capability

The skill's name and description match the declared requirement (the jirac binary). No unrelated binaries, credentials, or config paths are requested.

Instruction Scope

SKILL.md only instructs the agent to run jirac CLI commands and to verify local Jira authentication; it does not direct reading unrelated files, exfiltrating data, or contacting unexpected endpoints. It explicitly warns to treat Jira credentials and local attachments as sensitive and to confirm destructive actions.

Install Mechanism

No automated install spec is enforced by the registry; documentation points to standard sources (Homebrew, cargo, GitHub Releases). These are reasonable install options; user should prefer packaged releases or package managers and verify release integrity.

Credentials

The skill does not require environment variables or other credentials from the agent; it expects the user/environment to have already-authenticated jirac. Requesting Jira auth via the CLI is proportional to the stated functionality.

Persistence & Privilege

always is false and the skill does not request persistent system presence or modify other skills/configs. Autonomous invocation is allowed (platform default) but not combined with any broad or unexpected privileges.

Assessment

This skill is a thin adapter for the jirac CLI. Before installing or using it: (1) ensure you install jirac from a trusted source (prefer Homebrew, cargo, or the official GitHub Releases and verify artifacts), (2) confirm Jira authentication is configured securely in the environment (jirac stores credentials locally), (3) be cautious with attachments and bulk/destructive commands and require explicit confirmation before running them, and (4) if you do not want an agent to perform Jira actions autonomously, control when the skill can be invoked by reviewing agent policies or only using it interactively.

Use jirac as the Jira execution surface.

Requirements

• Require the jirac binary from the official jira-commands release source.
• Require Jira authentication to be configured before use, typically via jirac auth login in the target environment.
• Treat Jira credentials, local config, and attachment paths as sensitive.

Workflow

1. Verify jirac is installed by running jirac --version.
2. Verify authentication is already configured before issue operations, for example with jirac auth status or a known-good prior login.
3. Prefer direct jirac commands over raw Jira API calls when the CLI already supports the action.
4. Use jirac issue fields when required fields or custom fields are unclear.
5. Use jirac issue transition <KEY> without a transition argument when the target status is not known yet — shows an interactive picker.
6. Confirm intent before destructive or high-impact operations such as delete, bulk edits, transitions, and file attachments.

Common commands

# List and view
jirac issue list
jirac issue list -p PROJ
jirac issue list --jql 'project = PROJ AND status = "In Progress"'
jirac issue view PROJ-123

# Create
jirac issue create -p PROJ
jirac issue create -p PROJ -t Bug -s 'login crash' --assignee me
jirac issue create -p PROJ -t Story -s 'auth flow' --sprint 'Sprint 24' --field story_points=5
jirac issue create -p PROJ -t Sub-task -s 'sub-task' --parent PROJ-100

# Update
jirac issue update PROJ-123 --summary 'New title'
jirac issue update PROJ-123 --priority High --assignee me
jirac issue update PROJ-123 --labels backend,api --fix-versions v2.0
jirac issue update PROJ-123 --field story_points=8

# Transition (positional arg, not --to)
jirac issue transition PROJ-123              # interactive picker
jirac issue transition PROJ-123 'Done'
jirac issue transition PROJ-123 'In Progress'

# Comment and worklog
jirac issue comment add PROJ-123 --body 'QA verified in staging'
jirac issue worklog add PROJ-123 --time '2h' --comment 'Implementation work'

# Attach
jirac issue attach PROJ-123 ./screenshot.png

# Clone and delete
jirac issue clone PROJ-123
jirac issue clone PROJ-123 --project NEWPROJ --summary 'Copy: original'
jirac issue delete PROJ-123                  # prompts confirmation
jirac issue delete PROJ-123 --force

# Bulk operations
jirac issue bulk-transition --jql 'project = PROJ AND status = "To Do"' --to 'In Progress'
jirac issue bulk-update --jql 'project = PROJ AND assignee = EMPTY' --assignee me
jirac issue bulk-update --jql 'project = PROJ AND priority = Low' --priority High --force
jirac issue bulk-create --manifest issues.json

# Batch (mixed ops from manifest)
jirac issue batch --manifest ops.json

# Fields and JQL
jirac issue fields -p PROJ --issue-type Bug
jirac issue jql --run

Bulk-create manifest format

[
  {
    "project": "PROJ",
    "summary": "Issue title",
    "type": "Task",
    "assignee": "[e-mail]",
    "priority": "High",
    "labels": ["backend"],
    "parent": "PROJ-100",
    "description": "Markdown description",
    "fields": { "customfield_10016": 5 }
  }
]

Batch manifest format

[
  { "op": "create",     "project": "PROJ", "summary": "New task", "type": "Task" },
  { "op": "update",     "key": "PROJ-10",  "priority": "High", "assignee": "me" },
  { "op": "transition", "key": "PROJ-11",  "to": "Done" },
  { "op": "archive",    "key": "PROJ-12" }
]

Guidance

• Prefer interactive or metadata-assisted flows when field requirements are unclear.
• Confirm intent before operations that may change workflow state, bulk-edit, delete, or overwrite issue content.
• Confirm that local files selected for attachment are intended and safe to upload.
• Keep Jira project keys, issue keys, and status names exact.
• Prefer explicit project scoping in commands when working across multiple Jira projects.
• jirac issue transition takes a positional transition name/ID — not --to.

References

• Install guide: references/install.md