← ClaudeAtlas

log-jiralisted

Summarize the work done in this session and log it to Jira Cloud — create a task/story/subtask or log a worklog against an existing issue, using the jira-cli tool.
sharsh21/jira-cli · ★ 1 · AI & Automation · score 69
Install: claude install-skill sharsh21/jira-cli
# log-jira Use this skill when the user asks to "log this to jira", "log jira", "create a ticket for this", or similar, after doing work in the current session. This skill wraps a local CLI tool called `jira-cli` (a Node/TypeScript tool from the [jira-cli](../../README.md) repository, installed globally via `npm link`). It talks to Jira Cloud's REST API v3. Credentials live in `~/.jira-cli/config.json`, set up via `jira-cli config init`. Because `jira-cli` is a global command, this skill works from any project directory. ## Steps 1. **Check setup.** Run `jira-cli whoami`. If it fails because no config exists, tell the user to run `jira-cli config init` (interactive: base URL, email, API token, default project key) and stop — do not proceed until it succeeds. 2. **Draft a summary.** From the current conversation, write a 1-3 sentence summary of what was actually done (files changed, bug fixed, feature added). Don't ask the user for this — derive it yourself from context. Show it to the user as part of your questions so they can correct it. 3. **Ask the clarifying questions** (use `AskUserQuestion`, batched into as few questions as possible, only asking what you can't infer): - **Target**: log work against an **existing issue** (ask for the issue key) or **create a new issue**? - If creating: **issue type** (Task / Story / Bug), and **standalone or subtask** (if subtask, ask for the parent issue key). - **Original time estimate** — always ask this when creating a