Run any Skill in Manus with one click

resolve-random-jira-issue

Stars0

Forks0

UpdatedApril 27, 2026 at 08:42

Use when resolving random JIRA issues. Fixes bugs, refactors code, performs code and security reviews, ensures 100% test coverage, runs CI checks, and creates pull requests. Links PRs to JIRA issues and updates issue status.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

pekral

pekral/pekral.cz

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	resolve-random-jira-issue
description	Use when resolving random JIRA issues. Fixes bugs, refactors code, performs code and security reviews, ensures 100% test coverage, runs CI checks, and creates pull requests. Links PRs to JIRA issues and updates issue status.
license	MIT
metadata	{"author":"Petr Král (pekral.cz)"}

Constraint:

For all GitHub operations, prefer GitHub CLI (gh) as the primary tool.
If gh is not available or cannot be used, use an available GitHub MCP server as fallback.
If neither gh nor a GitHub MCP server is available, stop and return a failed result explaining that required GitHub tools are missing.
Read project.mdc file
First, load all the rules for the cursor editor (.cursor/rules/.*mdc).
Before resolving a task, always switch to the main branch, download the latest changes, and make sure you have the latest code in the main branch.
I want the texts to be in the language in which the assignment was written.
If you are not on the main git branch in the project, switch to it.
For comments posted to JIRA, always use JIRA Wiki Markup (not Markdown) and follow the universal structure from JIRA-focused skills.
Pull request creation is mandatory for every resolved JIRA issue selected by this skill. Do not finish without a GitHub PR URL linked to the selected JIRA issue.

Steps:

Log into JIRA and load all issues using the acli console tool first. If acli is not available, use the JIRA MCP server if available. If neither is available, stop and display a message stating that at least one of these tools must be installed to use the skill. List only those issues that are to be resolved by AI (they are tagged). Look for tasks labeled "Resolve_by_AI." If you are supposed to search in other places as well, find those other places too. Only not resolved issues should be listed!
Randomly select one and try to resolve it. Use the skill @.cursor/skills/resolve-jira-issue/SKILL.md.
Completion is valid only when the delegated flow creates a GitHub PR and links it in the selected JIRA issue.

Output Humanization

Use blader/humanizer for all skill outputs to keep the text natural and human-friendly.

More from this repository

same repository

analyze-problem

pekral/pekral.cz

Use when structured problem analysis for debugging, root cause identification, and breaking down complex issues before proposing solutions

2026-06-150

answer-pr-questions

pekral/pekral.cz

Analyze issue and pull request discussions, find unanswered current questions, and prepare concise unified answers for project managers or clients in plain language. Use when stakeholders need non-technical answers from GitHub issue/PR threads.

2026-04-270

create-jira-issue-from-pr

pekral/pekral.cz

Use when preparing a JIRA issue draft from GitHub pull request context while preserving the original assignment text and making the output understandable for both AI agents and non-technical stakeholders.

2026-04-270

package-review

pekral/pekral.cz

Use when reviewing composer.json packages. Validates structure, checks required fields, verifies links, and ensures proper configuration of autoloading, dependencies, and metadata.

2026-04-270

postman-collections

pekral/pekral.cz

Use when AI creates or modifies API endpoints and you need to generate or update Postman collections, keep request examples aligned with routes, and verify the collection is importable and runnable.

2026-04-270

race-condition-review

pekral/pekral.cz

Use when reviewing code for race conditions, concurrency issues, and shared-state consistency problems. Analyzes read-modify-write patterns, concurrent access to shared resources, and missing atomicity guards. Provides structured findings with severity levels and concrete fixes.

2026-04-270

name	resolve-random-jira-issue
description	Use when resolving random JIRA issues. Fixes bugs, refactors code, performs code and security reviews, ensures 100% test coverage, runs CI checks, and creates pull requests. Links PRs to JIRA issues and updates issue status.
license	MIT
metadata	{"author":"Petr Král (pekral.cz)"}

Constraint:

For all GitHub operations, prefer GitHub CLI (gh) as the primary tool.
If gh is not available or cannot be used, use an available GitHub MCP server as fallback.
If neither gh nor a GitHub MCP server is available, stop and return a failed result explaining that required GitHub tools are missing.
Read project.mdc file
First, load all the rules for the cursor editor (.cursor/rules/.*mdc).
Before resolving a task, always switch to the main branch, download the latest changes, and make sure you have the latest code in the main branch.
I want the texts to be in the language in which the assignment was written.
If you are not on the main git branch in the project, switch to it.
For comments posted to JIRA, always use JIRA Wiki Markup (not Markdown) and follow the universal structure from JIRA-focused skills.
Pull request creation is mandatory for every resolved JIRA issue selected by this skill. Do not finish without a GitHub PR URL linked to the selected JIRA issue.

Steps:

Log into JIRA and load all issues using the acli console tool first. If acli is not available, use the JIRA MCP server if available. If neither is available, stop and display a message stating that at least one of these tools must be installed to use the skill. List only those issues that are to be resolved by AI (they are tagged). Look for tasks labeled "Resolve_by_AI." If you are supposed to search in other places as well, find those other places too. Only not resolved issues should be listed!
Randomly select one and try to resolve it. Use the skill @.cursor/skills/resolve-jira-issue/SKILL.md.
Completion is valid only when the delegated flow creates a GitHub PR and links it in the selected JIRA issue.

Output Humanization

Use blader/humanizer for all skill outputs to keep the text natural and human-friendly.