- Home
- Skills
- Questnova502
- Claude Skills Sync
- Jira Integration
jira-integration_skill
- Python
1
GitHub Stars
9
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill questnova502/claude-skills-sync --skill jira-integration- AGENTS.md3.8 KB
- CHANGELOG.md13.4 KB
- CLAUDE.md3.8 KB
- composer.json527 B
- LICENSE1.1 KB
- MIGRATION.md7.5 KB
- PRD.md24.0 KB
- README.md6.4 KB
- SKILL.md2.5 KB
Overview
This skill provides Jira wiki markup syntax validation, ready-to-use templates, and practical formatting guidance for writing issue descriptions and comments. It helps convert Markdown to Jira wiki markup, enforces Jira-specific conventions (headings, code blocks, lists, tables), and includes quick references and templates for bug reports and feature requests.
How this skill works
The skill inspects text for common Markdown-to-Jira mistakes and validates Jira wiki constructs (headings, bold/italic, code blocks, lists, links, tables, panels, colors). It offers templates you can fill and a validation checklist and script to run locally before submission. Use the guidance to convert triple-backtick code blocks to {code:lang} and Markdown headings to h2./h3. formats.
When to use it
- Writing Jira issue descriptions or comments and ensuring they render correctly
- Converting Markdown content (README, PR notes) into Jira wiki markup
- Preparing bug reports or feature requests using provided templates
- Validating Jira syntax before creating or updating issues
- Checking code blocks, headings, lists, links, and tables follow Jira markup
Best practices
- Use h2. and h3. with a space after the period instead of Markdown ##/###
- Wrap code blocks with {code:language}...{code} and inline code with {{code}}
- Prefer *bold* and _italic_ Jira forms rather than Markdown asterisks or underscores
- Format links as [label|url] and reference issues as [PROJ-123]
- Run the provided validation script before submitting to catch common mistakes
Example use cases
- Convert a Markdown release note into Jira wiki markup for a release ticket
- Fill the bug report template with Environment, Steps to Reproduce, and Error Messages
- Create a feature request using the feature template: Overview, User Stories, Acceptance Criteria
- Validate and fix formatting issues in a long technical comment (tables, panels, colors)
- Ensure code samples in an issue use language-tagged {code:java} blocks for proper rendering
FAQ
Replace Markdown ##/### with h2. or h3. and include a space after the period (e.g., h2. Title).
What replaces triple backtick code fences?
Use {code:language}...{code} for code blocks and {{code}} for inline code.