atlassian

What it is good at

• Looking before it creates an issue

  A create call fails when the project key, the issue type name or a required field is wrong, and issue type names are per-project: Task in one project may be Story or Work Item in another. The skill reads the projects, types and required fields first, which costs one call and saves a confusing 400.

• Showing a bulk create before sending it

  --dry-run prints the exact payload for every issue and sends nothing. A real batch paces itself at five requests a second to stay inside Jira's limit and reports created and failed counts at the end.

• Writing a body Atlassian will accept

  The REST API wants Atlassian Document Format rather than a string, which is the detail that turns a two-line script into an afternoon. You author in a small HTML dialect and the conversion happens locally, so panels, status lozenges and task lists survive instead of collapsing to plain paragraphs.

• Proving it can reproduce a page before it edits one

  An update replaces the whole body, so anything the tool failed to understand on the way in is gone on the way out. Before writing, it converts the live page out and back and compares the result against what the server holds. If a single node differs it refuses and names the type. Measured against a real site it reproduces every page sampled: the oldest, the newest, and a plain alphabetical sweep. The check runs before every write.

• Carrying through what it does not recognise

  Atlassian's format is wider than any converter's vocabulary, and every macro on a page is a node this one has never heard of. Rather than dropping them or giving up, it carries each one through untouched, so changing a paragraph leaves the macros, colours, images and inline comments around it byte for byte as they were.

• Refusing a stale edit rather than overwriting one

  You pass the version your change was based on. Re-reading the page immediately before writing looks like a safeguard and is the opposite of one - it makes the version number current at the instant of the write, which is exactly what stops the clash being noticed. Passing the base version is what lets somebody else's edit be caught instead of buried.

• Publishing a repository's markdown to a space

  A folder of documentation goes up as Confluence pages, which is the job that otherwise gets done by hand once and then never again. Pages are created and updated, so a second run is a refresh rather than a pile of duplicates.

• Keeping the token off the command line

  curl reads the site, the credentials and the method from a config file at mode 600, so the token never appears in ps output or in shell history. Setup verifies it against your site before writing anything, so a wrong token costs you nothing.