skills/jira-syntax/SKILL.md
Use when writing or formatting Jira descriptions, comments, or any text destined for Jira. Converts Markdown to Jira wiki markup, provides templates (bug reports, feature requests), and validates syntax before submission. Trigger on any Jira content authoring task.
npx skillsauth add netresearch/jira-skill jira-syntaxInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Jira wiki markup syntax, templates, and validation. For API operations, use the jira-communication skill.
| Jira Syntax | Purpose | NOT this (Markdown) |
|-------------|---------|---------------------|
| h2. Title | Heading | ## Title |
| *bold* | Bold | **bold** |
| _italic_ | Italic | *italic* |
| {{code}} | Inline code | `code` |
| {code:java}...{code} | Code block | java ``` |
| [text\|url] | Link | [text](url) |
| [PROJ-123] | Issue link | - |
| [~username] | User mention | @username |
| * item | Bullet list | - item |
| # item | Numbered list | 1. item |
| \|\|Header\|\| | Table header | \|Header\| |
See references/jira-syntax-quick-reference.md for complete syntax documentation.
Path: templates/bug-report-template.md
Sections: Environment, Steps to Reproduce, Expected/Actual Behavior, Error Messages, Technical Notes
Path: templates/feature-request-template.md
Sections: Overview, User Stories, Acceptance Criteria, Technical Approach, Success Metrics
Run before submitting to Jira:
${CLAUDE_SKILL_DIR}/scripts/validate-jira-syntax.sh path/to/content.txt
h2. Title (space after period)*text* (single asterisk){code:language}...{code}* for bullets, # for numbers[label|url] or [PROJ-123]||Header|| and |Cell|{color:red}text{color}{panel:title=X}...{panel}| ❌ Wrong | ✅ Correct |
|---------|-----------|
| ## Heading | h2. Heading |
| **bold** | *bold* |
| `code` | {{code}} |
| [text](url) | [text\|url] |
| - bullet | * bullet |
| h2.Title | h2. Title |
Workflow:
${CLAUDE_SKILL_DIR}/scripts/validate-jira-syntax.shreferences/jira-syntax-quick-reference.md - Complete syntax documentationreferences/cross-project-refs.md - GitLab cross-project ref convention (group/project!N, group/project#N, group/project@tag) when linking to GitLab from Jiratemplates/bug-report-template.md - Bug report templatetemplates/feature-request-template.md - Feature request template${CLAUDE_SKILL_DIR}/scripts/validate-jira-syntax.sh - Automated syntax checkertools
Use when interacting with Jira issues - searching, creating, updating, moving, transitioning, commenting, logging work, downloading attachments, managing sprints, boards, issue links, web links, fields, or users. Auto-triggers on Jira URLs and issue keys (PROJ-123). Also use when MCP Atlassian tools fail or are unavailable for Jira Server/DC.
tools
Use when interacting with Jira issues - searching, creating, updating, moving, transitioning, commenting, logging work, downloading attachments, managing sprints, boards, issue links, web links, fields, or users. Auto-triggers on Jira URLs and issue keys (PROJ-123). Also use when MCP Atlassian tools fail or are unavailable for Jira Server/DC.
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.