Jira Wiki Markup

Internal shared skill. Single source of truth for Jira Wiki notation (Wiki renderer / Server/DC). Hosts and other comment writers declare it in dependencies, abort if missing, and load it immediately before composing a wiki-rendered field. This skill does not call the Jira API and does not own status transitions.

Prerequisite check: this skill has no further skill dependencies. Referencing skills abort when this skill is missing (install: npx skills add FuDesign2008/open-skills -g --skill '*' --yes).

When to load

Load this skill in the same turn as composing any Jira field that the Wiki renderer will display — typically jira_add_comment's body. Hosts keep the semantic field map (branch, commit, URL, root cause); this skill owns how those values are marked up.

Full notation tables and the canonical repair-comment skeleton: reference.md.

Composition

Write Wiki markup, not GitHub Markdown. The Wiki renderer is a different dialect.

Links: put a space after a URL when the next character is not part of the URL. Images: !https://example.com/image.png! or !attached.png|thumbnail!.

Markup fidelity across write channels

Composing correct markup is necessary but not sufficient: a relaying layer may escape or rewrite it while still returning success. After writing any Wiki-rendered field — comment body, description, or another wiki field — read the stored value back and confirm the key markers survive verbatim: h3./h4. line starts, *bold*, {{mono}}, [label|url]. When the stored value cannot be read back at all, treat the write as unverified and report it.

On escaped or rewritten markers (\*bold\*, h3. turned into ###), retry through an available direct-REST channel for the same field. A channel is available only when its writing script and its credential resolver both exist; a skill directory alone is not enough, because the script cannot run without the resolver. If a Jira writeback skill that ships a direct-write script is installed (for example jira-status-writeback), the comment-body fallback is scripts/update-comment-wiki.mjs, which resolves credentials through the jira-read chain. That script covers comment bodies only: descriptions and other fields need an equivalent REST endpoint. With no available channel, report the fidelity failure and the missing fallback instead of claiming success.

The post-merge repair-comment flow restates this discipline as a requirement in jira-status-writeback; this section covers every other wiki-field write.

Repair comment

When a host or jira-status-writeback posts a post-merge repair comment, format the host field map with the canonical skeleton in reference.md: report title h3., verification section h4., bold labels *Field*:, each scenario a numbered item # *{name}* (bold name, not _italic_). Wiki # is that numbered list — leave it as #, not h1./h2.. Omit a field only when the host marks it N/A.

Integration

• Declare jira-wiki-markup in frontmatter dependencies.
• Load it before composing the wiki field; pass through host field values unchanged except for markup wrapping.
• Keep in the host: when the comment is written, and the semantic field map only.
• Orientation: referenced by Jira comment writers via frontmatter dependencies (no integrator-name roster).