jira-task-executor

Implements a Jira issue end-to-end from its git worktree through commit, push, and pull request.

1|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/kantorv/jira-sdlc-tools --skill jira-task-executor-kantorv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-task-executor
Source: https://github.com/kantorv/jira-sdlc-tools/tree/main/plugins/jira-sdlc/skills/jira-task-executor
Command: npx skills add https://github.com/kantorv/jira-sdlc-tools --skill jira-task-executor-kantorv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the manual coordination of picking up a Jira issue, transitioning its status, implementing the change in an isolated git worktree, running tests, committing, pushing, and opening a pull request, all while keeping Jira comments as durable task memory across sessions. ## Core Features & Use Cases - End-to-end issue implementation: Derives the issue key from the current branch, transitions Jira status, investigates the codebase, implements, tests, commits, pushes, and opens or updates the PR. - Review-reject recovery: On re-run after a reviewer rejects the PR, it reads the reviewer's findings from Jira comments and updates the existing PR instead of opening a duplicate. - Task memory via Jira comments: Records durable findings and decisions as marked Jira comments so later sessions inherit context instead of starting cold. - Use Case: A developer runs the skill bare from inside the worktree created by jira-task-assigner; the skill implements the issue, runs the project's tests, and reports back the PR link and new Jira status. ## Quick Start Run the jira-task-executor skill from inside the issue's own git worktree with no arguments to implement the Jira issue tied to the current branch.

Frequently Asked Questions about jira-task-executor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a Jira issue automatically from a git worktree?

Run the skill bare from inside the issue's own worktree created by jira-task-assigner. The issue key is derived from the branch name, and the skill handles status transition, implementation, tests, commit, push, and the pull request.

How do I fix a rejected pull request review in Jira?

Re-run the skill the same way from the same worktree. It reads the reviewer's CHANGES REQUESTED findings from the issue's comments, applies the fixes, and updates the existing PR instead of opening a second one.

Does the skill work outside a linked git worktree?

No. The statuscheck healthcheck stops the run unless you are on a feature or hotfix branch inside a linked worktree. You must cd into the worktree created by jira-task-assigner and rerun.

What happens when tests fail before committing?

Failed tests are re-run individually to rule out flakiness. If an individually re-run test still fails, the skill stops, reports the failure, and waits for instructions without committing, pushing, or opening a PR.

Can I pass an issue key as an argument to the skill?

No. The issue key always comes from the current branch name, never from an argument. Any argument passed is treated as free-form notes that supplement the issue description for that run.