search-jira-issues

# Search Jira Issues !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh` !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-context.sh search-jira-issues` > **Configuration**: Set `work.integration: jira` and > `work.default_project_code: <KEY>` in `.accelerator/config.md` to > enable auto-scoping. See the > [`### work` section of `configure/SKILL.md`](../../config/configure/SKILL.md#work) > for the full reference. Search a Jira Cloud tenant using structured flags that compose into safe JQL. Work through the steps below in order. ## Step 1: Parse the flag set Read the argument string and note each flag. Two conventions worth explaining to the user when their intent maps to them: - **Negation prefix**: any value-bearing flag accepts a leading `~` to mean "NOT". `--status '~Done'` → `status NOT IN ('Done')`. `--label '~stale'` → `labels NOT IN ('stale')`. Same for `--type`, `--component`, `--reporter`, `--parent`, `--assignee`. Quote the value to keep the shell from expanding `~`. - **`--fields` accepts both forms**: comma-separated (`--fields summary,status`) and repeatable (`--fields summary --fields status`) work identically and may be mixed. Prefer structured flags whenever the user's intent maps to one (assignee, status, label, type, component, reporter, parent, free-text). The `--all-projects` flag omits the project clause entirely when the user explicitly wants to search across all projects. ## Step 2: Trust boundary on `--jql` Only pass `--jql 'c...