Skill
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...
When to use jirac
Choose if
You're inside an OpenClaw or Claude Code session and need to manage Jira issues end-to-end from the CLI — create, list, view, update, transition, comment, log work, attach files, clone, and run bulk operations. The skill standardizes confirmations before destructive actions and prefers `jirac` commands over raw API calls.
Avoid if
You can't install the `jirac` binary on the host (it's the hard dependency). You need a Jira capability beyond what `jirac` covers (custom workflows, advanced JQL features, scripted REST calls). You want zero-touch automation — the skill insists on human confirmation for destructive ops.
Risk Flags
- MEDIUM auth Requires `jirac` CLI binary installed plus pre-configured Jira credentials via `jirac auth login`. Agents on hosts without the binary or auth state cannot execute any operation.
- LOW scope Skill enforces explicit confirmation before destructive operations (delete, bulk edits, transitions, attachments). README treats credentials and file paths as sensitive — agents must surface confirmation prompts.
- LOW scope Bounded by underlying Jira instance permissions and the supported `jirac` CLI commands. No raw Jira REST API surface — features unsupported by jirac are out of scope.
Cost
Type: Free
Distribution
- ClawHub
jirac- License
- MIT-0