How do I install the Jira Edit Issue skill?

Run npx skillmds@latest add arfar-x/jira-edit-issue in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Jira Edit Issue safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Jira Edit Issue?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Jira Edit Issue free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Jira Edit Issue?

arfar-x (@arfar-x) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Jira Edit Issue by arfar-x — Agent Skill

Name: Jira Edit Issue
Author: arfar-x

Jira Edit Issue

Updates fields (summary, description, labels, assignee, priority, components) on an existing Jira issue or subtask. Use for "rename PAY-123", "reassign PAY-123 to John", "add the Backend label to PAY-101". This is a write operation gated behind explicit user confirmation. For moving an issue between statuses, use jira-status instead.

arfar-x Updated Sep 21, 2026

File contents

Jira: Edit Issue

Write, gated. Run from this skill's directory:

python3 ../jira/scripts/jira_tool.py edit_issue --issue_key PAYKAN-123 \
  --summary "New title" --confirm

Works the same way on a subtask -- just pass the subtask's own --issue_key.

(First-time setup, once per environment: pip install -r ../jira/requirements.txt.)

--issue_key is required; at least one of --summary, --description, --labels (comma-separated, replaces the existing list), --assignee_account_id, --priority, --components (comma-separated, replaces the existing list), --custom_fields (a JSON object of customfield_NNNNN -> value -- resolve ids/shapes via python3 ../jira/scripts/jira_tool.py list_fields first, never guess either) must be given. Omitted fields are left unchanged.

Assignee

--assignee_account_id needs a Jira account_id, not a display name -- resolve one via jira-search-users first rather than guessing.

Also requires JIRA_DEPLOYMENT_TYPE (cloud or server) to be set: Jira Cloud identifies users by accountId, Server/Data Center by username, and the tool won't guess which one this instance is. If the result is an "error" naming JIRA_DEPLOYMENT_TYPE, tell the user to set that environment variable once -- it isn't something to retry around.

Confirmation

This refuses to execute unless run with --confirm (enforced in code, not just prompted). Unless JIRA_AUTO_CONFIRM_WRITES=true is set:

State exactly which fields you're about to change and to what value, and wait for the user's explicit yes.
Only then re-run the same command with --confirm appended.
If the result has "requires_confirmation": true, treat that as the tool declining to act -- relay pending_action to the user and ask, don't retry with --confirm on your own.

If the result contains "error", tell the user what went wrong in plain language instead of retrying silently or fabricating a result.

See ../jira/README.md for architecture details and the full environment-variable table.

---name: jira-edit-issuedescription: Updates fields (summary, description, labels, assignee, priority, components) on an existing Jira issue or subtask. Use for "rename PAY-123", "reassign PAY-123 to John", "add the Backend label to PAY-101". This is a write operation gated behind explicit user confirmation. For moving an issue between statuses, use jira-status instead.---# Jira: Edit Issue**Write, gated.** Run from this skill's directory:```bashpython3 ../jira/scripts/jira_tool.py edit_issue --issue_key PAYKAN-123 \ --summary "New title" --confirm```Works the same way on a subtask -- just pass the subtask's own`--issue_key`.(First-time setup, once per environment: `pip install -r ../jira/requirements.txt`.)`--issue_key` is required; at least one of `--summary`, `--description`,`--labels` (comma-separated, replaces the existing list), `--assignee_account_id`,`--priority`, `--components` (comma-separated, replaces the existing list),`--custom_fields` (a JSON object of `customfield_NNNNN -> value` -- resolveids/shapes via `python3 ../jira/scripts/jira_tool.py list_fields` first,never guess either) must be given. Omitted fields are left unchanged.## Assignee`--assignee_account_id` needs a Jira `account_id`, not a display name --resolve one via `jira-search-users` first rather than guessing.Also requires `JIRA_DEPLOYMENT_TYPE` (`cloud` or `server`) to be set:Jira Cloud identifies users by `accountId`, Server/Data Center byusername, and the tool won't guess which one this instance is. If theresult is an `"error"` naming `JIRA_DEPLOYMENT_TYPE`, tell the user toset that environment variable once -- it isn't something to retryaround.## ConfirmationThis refuses to execute unless run with `--confirm` (enforced in code, notjust prompted). Unless `JIRA_AUTO_CONFIRM_WRITES=true` is set:1. State exactly which fields you're about to change and to what value, and wait for the user's explicit yes.2. Only then re-run the same command with `--confirm` appended.3. If the result has `"requires_confirmation": true`, treat that as the tool declining to act -- relay `pending_action` to the user and ask, don't retry with `--confirm` on your own.If the result contains `"error"`, tell the user what went wrong in plainlanguage instead of retrying silently or fabricating a result.See `../jira/README.md` for architecture details and the fullenvironment-variable table.

Frequently asked questions