Agent skill

Jira Implement Task

by commercetools in commercetools/ui-kit

Fetch Jira ticket, create branch, implement changes, commit, push, open PR.

MITAuto-check: notesDevelopment

Install Jira Implement Task

skills CLI

$ npx skills add commercetools/ui-kit --skill jira-implement-task -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install commercetools/ui-kit jira-implement-task --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/commercetools/ui-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/jira-implement-task .claude/skills/jira-implement-task && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "jira-implement-task" agent skill from https://github.com/commercetools/ui-kit/tree/main/.agents/skills/jira-implement-task into .claude/skills/jira-implement-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jira-implement-task", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/commercetools/ui-kit/tree/main/.agents/skills/jira-implement-task

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add commercetools/ui-kit --skill jira-implement-task -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install commercetools/ui-kit jira-implement-task --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/commercetools/ui-kit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/jira-implement-task .agents/skills/jira-implement-task && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "jira-implement-task" agent skill from https://github.com/commercetools/ui-kit/tree/main/.agents/skills/jira-implement-task into .agents/skills/jira-implement-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jira-implement-task", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add commercetools/ui-kit --skill jira-implement-task -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install commercetools/ui-kit jira-implement-task --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/commercetools/ui-kit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/jira-implement-task .cursor/skills/jira-implement-task && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "jira-implement-task" agent skill from https://github.com/commercetools/ui-kit/tree/main/.agents/skills/jira-implement-task into .cursor/skills/jira-implement-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jira-implement-task", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/commercetools/ui-kit.git --path .agents/skills/jira-implement-task

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add commercetools/ui-kit --skill jira-implement-task -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install commercetools/ui-kit jira-implement-task --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/commercetools/ui-kit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/jira-implement-task .gemini/skills/jira-implement-task && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "jira-implement-task" agent skill from https://github.com/commercetools/ui-kit/tree/main/.agents/skills/jira-implement-task into .gemini/skills/jira-implement-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jira-implement-task", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install commercetools/ui-kit jira-implement-task

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add commercetools/ui-kit --skill jira-implement-task -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/commercetools/ui-kit.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/jira-implement-task .github/skills/jira-implement-task && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "jira-implement-task" agent skill from https://github.com/commercetools/ui-kit/tree/main/.agents/skills/jira-implement-task into .github/skills/jira-implement-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jira-implement-task", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add commercetools/ui-kit --skill jira-implement-task -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install commercetools/ui-kit jira-implement-task --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/commercetools/ui-kit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/jira-implement-task .opencode/skills/jira-implement-task && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "jira-implement-task" agent skill from https://github.com/commercetools/ui-kit/tree/main/.agents/skills/jira-implement-task into .opencode/skills/jira-implement-task/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jira-implement-task", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: jira-implement-task
GitHub stars: 154
Token cost: ~1.6k tokens
SKILL.md length: 743 words
Files: 1
Skills in repo: 11
Repo updated: Oct 3, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Fetch Jira ticket, create branch, implement changes, commit, push, open PR.

Works in 5 steps: Verify Restore Context → Fetch Ticket Details → Create a Feature Branch → …
Tasks that involve Git workflow
SKILL.md covers Argument Parsing, Step 0: Verify Restore Context, Project Configuration and Step 1: Fetch Ticket Details, plus 3 more sections
Calls git, gh and pnpm; reaches claude.com

What it does

Jira Implement Task is an agent skill from commercetools/ui-kit. Fetch Jira ticket, create branch, implement changes, commit, push, open PR.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git workflow and Design systems. It works with Jira. The licence is MIT.

When your agent uses it

Tasks that involve Git workflow
Tasks that involve Design systems

Example prompts

“/jira-implement-task”

Requirements

Pre-approved tools (allowed-tools): Bash, Grep, Glob, Read, Edit, Write, Agent

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Verify Restore Context
Fetch Ticket Details
Create a Feature Branch
Implement Changes
Push and Create PR

What it can do on your machine

Read from SKILL.md and the folder at commit 62ca335. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Bash
- Grep
- Glob
- Read
- Edit
- Write
- Agent
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
- gh
- pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- claude.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Jira Implement Task loads about 1.6k tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 743 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~24
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Bash, Grep, Glob, Read, Edit, Write, Agent
```

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from commercetools/ui-kit at commit 62ca335, republished under its MIT licence (© commercetools). 743 words, ~1,606 tokens.

Download SKILL.mdSave it as .claude/skills/jira-implement-task/SKILL.md (or your agent's skills folder).

name: jira-implement-task
description: Fetch Jira ticket, create branch, implement changes, commit, push, open PR.
allowed-tools: Bash, Grep, Glob, Read, Edit, Write, Agent
disable-model-invocation: false
argument-hint: <ticket-key>
scope: jira

Implement Jira Task

You are a software engineer. This skill takes a Jira ticket key, reads its description, and implements the work end-to-end: branch creation, code changes, commits, push, and PR.

Argument Parsing

Parse $ARGUMENTS to extract:

Ticket key: The Jira ticket key (e.g., FEC-123). Required.

Restore Context

This skill uses /agent-restore-context as a safety net in case /compact or /clear happens mid-implementation.

Step 0: /agent-restore-context check to verify the hook is set up.

Step 3a: /agent-restore-context write jira-implement-task once after creating the implementation plan.

Step 3c: /agent-restore-context delete jira-implement-task when done.

Step 0: Verify Restore Context

Invoke /agent-restore-context check. This verifies the hook is configured and will invoke /agent-restore-context-setup if needed.

Project Configuration

Before starting, read the project's CLAUDE.md and/or AGENTS.md to determine the following project-specific settings. These files are the source of truth for how to work in this repo.

Setting	What to look for	Fallback default
Test command (files)	Command to run tests for specific files/folders	`pnpm test <files>`
Test command (full)	Command to run the full test suite	`pnpm test`
Branch naming	Branch naming convention or prefix rules	`<TICKET-KEY>-<slug>`
Base branch	Default branch to branch from	`main`
Commit format	Commit message convention	Conventional commits
Component workflow	Command/process for new components (e.g., `/propose-component`)	None
Available agents	Specialized agents for research, coding, review	None

If a setting is not found in CLAUDE.md, AGENTS.md, rules/, or /docs, ask the user whether they want to add it to CLAUDE.md, AGENTS.md, rules/ or /docs — or use the fallback default for this run only.

Step 1: Fetch Ticket Details

Use the Atlassian MCP tools to retrieve the ticket:

Call mcp__atlassian__getAccessibleAtlassianResources to get the cloud ID
Call mcp__atlassian__getJiraIssue with the cloud ID and ticket key
Extract: Summary, Description (requirements, acceptance criteria, files), and Issue type

If the ticket cannot be found, report the error and stop. Always write Markdown to Jira, never ADF — the MCP tools handle conversion.

Step 2: Create a Feature Branch

Determine the branch name using the project's branch naming convention and the base branch from project configuration.

Create a branch from the base branch in the current working tree:

bash

git checkout <base-branch>
git pull
git checkout -b <branch-name>

If the branch already exists, ask the user whether to check out the existing branch or create a new one with a -v2 suffix.

Step 3: Implement Changes

3a: Understand Scope and Plan

Understand scope: Read the ticket description carefully. Identify all files to modify/create.
Read existing files: Always read files before modifying them.
Create implementation plan: Break the changes into the smallest reasonable chunks of work. Save the plan to <skills-dir>/jira-implement-task/plans/<TICKET-KEY>-plan.md (where <skills-dir> is .agents/skills/ or .claude/skills/ per the detected layout). Each task should be independently testable and committable. Commit the plan so it can be shared for handoff. Delete it before merging or keep it as a record.
Create restore context: Invoke /agent-restore-context write jira-implement-task with content that includes the ticket key, branch name, plan file path, and the instruction to read the plan file before doing any work.

Show full SKILL.md (245 more words)Show less

3b: Implement Each Task (Red/Green TDD)

For each task in the implementation plan:

Write tests first (red phase): Write or update tests that capture the expected behavior. Tests should fail at this point.
Implement changes (green phase): Write the minimum code to make the tests pass.
Run tests: Verify all tests pass using the project's test command (files).
Commit: Commit the tests and implementation together.

If stuck after 3 attempts on a task, stop and ask the user for guidance.

3c: Completion

Once all tasks in the plan are implemented and passing:

Run full test suite: Run the project's test command (full) to verify everything passes.
Invoke /agent-restore-context delete jira-implement-task.
Ask the user whether to delete the implementation plan file or keep it.
Proceed to Step 4 (push and PR creation).

Guidelines

Follow the project's conventions from CLAUDE.md / AGENTS.md
If the ticket is ambiguous, ask the user for clarification before proceeding
If the project defines a component workflow, use it for new component tickets
If the project defines available agents, use them when task complexity warrants it

Step 4: Push and Create PR

Permission check

Run gh repo view --json viewerPermission --jq '.viewerPermission'. If the result is READ, skip push and PR — print the exact git push and gh pr create commands for the user to run manually, then stop.

Push and create PR

bash

git push -u origin <branch-name>
gh pr create --title "<type>(<scope>): <summary>" --body "$(cat <<'EOF'
## Summary
<1-5 bullet points describing the changes>

Closes <TICKET-KEY>

## Test plan
- [ ] <verification steps>

🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"

Return the PR URL to the user when done.

Implement Jira task: $ARGUMENTS

Files

Just SKILL.md in .agents/skills/jira-implement-task of commercetools/ui-kit.

Open the folder on GitHubat commit 62ca335

Compare with similar skills

Jira Implement Task next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Jira Implement Task compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Jira Implement Task this skillcommercetools/ui-kit	154	—	~1.6k	Automated safety check: Notes	MIT	4 days ago
Project Session ManagerYeachan-Heo/oh-my-claudecode	40k	—	~4k	Automated safety check: Pass	MIT	today
Version Control StrategyOwl-Listener/designer-skills	2.9k	1 repos	~467	Automated safety check: Pass	MIT	1 mo ago
Speckit Git Featureopsmill/infrahub	529	—	~638	Automated safety check: Pass	Apache-2.0	today
Jirasd0xdev/sd0x-harness	192	—	~1.9k	Automated safety check: Pass	MIT	yesterday
Lint Fixgetsentry/sentry	45k	—	~1k	Automated safety check: Pass	Custom licence	today

Similar skills

Project Session Manager
Yeachan-Heo/oh-my-claudecode
Creates isolated git worktrees, with optional tmux sessions, for PR reviews, issue fixes and feature work across projects and repositories.
40k GitHub stars~4k tokensUpdated today
DevelopmentAuto-check passed
Version Control Strategy
Owl-Listener/designer-skills
Define version control for design files, components, and libraries — branching, naming, and release.
2.9k GitHub starsUsed in 1 repo~467 tokens
Frontend & DesignAuto-check passed
Speckit Git Feature
opsmill/infrahub
Validate Jira/JPD ticket reference and create a feature branch
529 GitHub stars~638 tokensUpdated today
DevelopmentAuto-check passed
Jira
sd0xdev/sd0x-harness
Jira integration — view issues, generate branches, create tickets, transition status.
192 GitHub stars~1.9k tokensUpdated yesterday
DevelopmentAuto-check passed
Lint Fix
getsentry/sentry
Official
Fix violations of an eslintPluginScraps rule across the codebase.
45k GitHub stars~1k tokensUpdated today
DevelopmentAuto-check passed
Prototype First UI
DejavuMoe/Smoji
Run a safe prototype-first UI/UX workflow across web, desktop, mobile, extensions, and multimodal design inputs.
114 GitHub stars~4.2k tokensUpdated 4 days ago
DevelopmentAuto-check passed

Questions about Jira Implement Task

What does Jira Implement Task do?

Fetch Jira ticket, create branch, implement changes, commit, push, open PR. Jira Implement Task is an agent skill from commercetools/ui-kit. Fetch Jira ticket, create branch, implement changes, commit, push, open PR.

When should I use Jira Implement Task?

Jira Implement Task fits situations like: tasks that involve Git workflow; tasks that involve Design systems.

How do I install Jira Implement Task in Claude Code?

Run `npx skills add commercetools/ui-kit --skill jira-implement-task -a claude-code`. Or copy the skill folder (.agents/skills/jira-implement-task in commercetools/ui-kit) into .claude/skills/jira-implement-task in your project. Claude Code loads it when a task matches its description.

How do I install Jira Implement Task in Codex?

Run `npx skills add commercetools/ui-kit --skill jira-implement-task -a codex`. Or copy the skill folder (.agents/skills/jira-implement-task in commercetools/ui-kit) into .agents/skills/jira-implement-task in your project. Codex loads it when a task matches its description.

Can I use Jira Implement Task in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add commercetools/ui-kit --skill jira-implement-task -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jira-implement-task, .gemini/skills/jira-implement-task, .github/skills/jira-implement-task and .opencode/skills/jira-implement-task in your project.

What does Jira Implement Task need to run?

Going by SKILL.md and its folder, Jira Implement Task needs the command-line tools its instructions call (git, gh and pnpm). Its frontmatter pre-approves these tools: Bash, Grep, Glob, Read, Edit, Write, Agent.

Does Jira Implement Task access the network?

SKILL.md names 1 domain. In commands or code: claude.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Jira Implement Task safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Jira Implement Task use?

Jira Implement Task is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Jira Implement Task use?

About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Jira Implement Task?

Skills that share tags, products or a category with Jira Implement Task: Project Session Manager (Yeachan-Heo/oh-my-claudecode, 40k stars), Version Control Strategy (Owl-Listener/designer-skills, 2.9k stars), Speckit Git Feature (opsmill/infrahub, 529 stars) and Jira (sd0xdev/sd0x-harness, 192 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Jira Implement Task?

commercetools (a GitHub organization) maintains it in commercetools/ui-kit, which has 154 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 3, 2026.

Source: commercetools/ui-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Jira Implement Task

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Implement Jira Task

Argument Parsing

Step 0: Verify Restore Context

Project Configuration

Step 1: Fetch Ticket Details

Step 2: Create a Feature Branch

Step 3: Implement Changes

3a: Understand Scope and Plan

3b: Implement Each Task (Red/Green TDD)

3c: Completion

Guidelines

Step 4: Push and Create PR

Permission check

Push and create PR

Files

Compare with similar skills

Similar skills

More from commercetools/ui-kit

Related

Questions about Jira Implement Task