jiralisted

# Jira issue creation and lookup Create and read Jira Cloud issues through the REST v3 API, authenticated with an API token. This skill **creates and reads only**. It has no delete, no bulk transition, and no project administration. Anything destructive is done by a human in the Jira UI. ## Prerequisites - Credentials in `~/.dbhq/atlassian/config.json` - shared with `confluence`; run setup if absent - `jq`, `curl` and `column` (the last for `jira-meta.sh` and `search`/`mine`'s table output - `bsdextrautils` on Debian/Ubuntu, `util-linux` elsewhere; not guaranteed present) ## Setup ```bash ${CLAUDE_SKILL_DIR}/../_shared/scripts/atlassian-setup.sh ``` It asks for the site URL, the account email, and an API token from <https://id.atlassian.com/manage-profile/security/api-tokens>. The token input is hidden. It verifies Jira access against `/rest/api/3/myself` **before** writing anything, then checks Confluence access too (a warning, not a blocker - a token can be valid for Jira with no Confluence licence), and saves to `~/.dbhq/atlassian/config.json` at mode 600 only after both checks have run. Credentials live outside the repository and are never committed. ## Look before you create A create call fails when the project key, the issue type name, or a required field is wrong. Check first - it costs one call and saves a confusing 400. ```bash ${CLAUDE_SKILL_DIR}/scripts/jira-meta.sh projects [search] # project keys ${CLAUDE_SKILL_DIR}/scripts/jira-meta.sh types <PROJ