md-to-jira
Markdown to Jira Converter
Convert GitHub-flavored Markdown to Jira wiki markup syntax directly in the conversation.
Conversion Rules
1. Code Blocks (extract first, restore last)
Fenced code blocks with optional language:
```javascript
code here
```
becomes:
{code:javascript}
code here
{code}
Without language: {code}...{code}
2. Inline Code
`code` becomes {{code}}
3. Headers
# H1 → h1. H1
## H2 → h2. H2
### H3 → h3. H3
#### H4 → h4. H4
##### H5 → h5. H5
###### H6 → h6. H6
4. Bold and Italic
**bold**or__bold__→*bold**italic*→_italic_
Important: Process bold first (replace ** with Jira *), then convert remaining single * italic to _.
5. Strikethrough
~~text~~ → -text-
6. Images
 → !url|alt=alt! (or !url! if no alt text)
7. Links
[text](url) → [text|url]
8. Blockquotes
> text → bq. text
9. Horizontal Rules
---, ***, or ___ → ----
10. Unordered Lists (with nesting)
Nesting is determined by indentation (2 spaces per level):
- item → * item
- nested → ** nested
- deeper → *** deeper
11. Ordered Lists (with nesting)
1. item → # item
1. nested → ## nested
12. Tables
Markdown:
| H1 | H2 |
|----|-----|
| D1 | D2 |
Jira:
||H1||H2||
|D1|D2|
The separator row (|---|---|) is removed. Header cells use || delimiters, data cells use |.
How to Apply
- If the user provides markdown text directly, convert it and output the Jira markup.
- If the user points to a markdown file, read it, convert, and output the result.
- Always output the converted Jira markup in a code block so the user can copy it easily.
- If the input is large, process it section by section to avoid errors.
More from kadel/claude-plugins
jira cli usage
This skill should be used when the user asks to "interact with Jira", "list Jira issues", "create Jira issue", "manage sprints", "view epics", "search issues", "move issue status", "assign issue", or mentions using the jira command-line tool for project management.
13backstage custom resource
This skill should be used when the user asks to "create Backstage CR", "create RHDH custom resource", "configure rhdh-operator", "create Backstage manifest", "modify Backstage CR", "configure RHDH deployment", "add dynamic plugins to CR", "configure Backstage database", "set up Backstage route", "configure app-config for RHDH", "create rhdh.redhat.com/v1alpha Backstage", or mentions creating or modifying a Backstage Custom Resource for the rhdh-operator.
10worktree feature development
This skill should be used when the user asks to "start a new feature", "create feature branch in worktree", "set up isolated feature development", "work on feature in separate directory", or mentions git worktree for feature isolation.
10generate frontend wiring
This skill should be used when the user asks to "generate frontend wiring", "show frontend wiring", "create RHDH binding", "generate dynamic plugin config", "show plugin wiring for RHDH", "create app-config for frontend plugin", or wants to generate the RHDH dynamic plugin wiring configuration for an existing Backstage frontend plugin. The skill analyzes the plugin's source code and generates the appropriate configuration.
9rhdh frontend dynamic plugin bootstrap
This skill should be used when the user asks to "create RHDH frontend plugin", "bootstrap frontend dynamic plugin", "create UI plugin for RHDH", "new frontend plugin for Red Hat Developer Hub", "add entity card to RHDH", "create dynamic route", "add sidebar menu item", "configure mount points", "create theme plugin", or mentions creating frontend components, UI pages, entity cards, or visual customizations for Red Hat Developer Hub or RHDH. This skill is specifically for frontend plugins - for backend plugins, use the separate backend plugin skill.
9rhdh backend dynamic plugin bootstrap
This skill should be used when the user asks to "create RHDH backend plugin", "bootstrap backend dynamic plugin", "create backstage backend plugin for RHDH", "new backend plugin for Red Hat Developer Hub", "create dynamic backend plugin", "scaffold RHDH backend plugin", "new scaffolder action", "create catalog processor", or mentions creating a new backend plugin, backend module, or server-side functionality for Red Hat Developer Hub or RHDH. This skill is specifically for backend plugins - for frontend plugins, use the separate frontend plugin skill.
9