jiralisted

# Jira Access Reach for `acli` (Atlassian CLI) before doing anything else. ## Detection Trigger this rule when any of the following appears in the user's message: - A Jira-style key matching `[A-Z]+-\d+` `(review-time: trigger condition for the rule, not a rule itself)` - The words "Jira", "ticket", "issue", "story", "epic", "bug" used in a tracker sense (not a generic "there's an issue with X") `(review-time: trigger condition)` - A Jira URL (`*.atlassian.net/browse/KEY-123`) `(review-time: trigger condition)` If the reference is ambiguous (could be GitHub issue vs Jira), ask before assuming. `(review-time: requires judging ambiguity in the user's message)` ## Tool check 1. Run `which acli` to confirm it is installed. `(review-time: procedural step in a sequence)` 2. If installed, run `acli jira auth status` (or attempt a read command) to confirm it is authenticated. If unauthenticated, surface that to the user - do not attempt to authenticate on their behalf. `(review-time: procedural step)` 3. If not installed or not configured, tell the user and fall back to asking them for the ticket contents. `(review-time: error-handling pattern in conversation)` ## Usage Prefer `acli` over web fetches or asking the user to paste ticket content. Common commands: ```bash acli jira workitem view <KEY> # read a ticket acli jira workitem search --jql "..." # search acli jira workitem comment <KEY> ... # add comment acli jira workitem update <KEY> ... # update