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/jira/config.json` - run setup if absent - `jq` and `curl` ## Setup ```bash ${CLAUDE_SKILL_DIR}/scripts/jira-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 against `/rest/api/3/myself` **before** writing anything, then saves to `~/.dbhq/jira/config.json` at mode 600. 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 <PROJECT> # issue type names for that project ${CLAUDE_SKILL_DIR}/scripts/jira-meta.sh fields <PROJECT> <TYPE> # what a create accepts, required marked ${CLAUDE_SKILL_DIR}/scripts/jira-meta.sh priorities # valid priority names ${CLAUDE_SKILL_DIR}/scripts/jira-meta.sh whoami # who the token authenticates as ``` Issue type names are per-projec