How do I install the Jira Worklog Edit skill?

Run npx skillmds@latest add arfar-x/jira-worklog-edit 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 Worklog Edit 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 Worklog Edit?

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 Worklog Edit free to use?

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

Who published Jira Worklog Edit?

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

Jira Worklog Edit by arfar-x — Agent Skill

Name: Jira Worklog Edit
Author: arfar-x

Jira Worklog Edit

Updates an existing Jira worklog entry's duration, description, or date. Use for "fix that worklog", "I logged the wrong date, change it to Tuesday", "change the description on that time log". This is a write operation gated behind explicit user confirmation.

arfar-x Updated Sep 21, 2026

File contents

Jira: Worklog Edit

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

python3 ../jira/scripts/jira_tool.py worklog_edit --issue_key PAY-123 --worklog_id 28459 \
  [--duration 2h] [--description "..."] [--date 2026-07-20] --confirm

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

--issue_key and --worklog_id are required; at least one of --duration/--description/--date must also be given (omitted fields are left unchanged). Find --worklog_id via the jira-issue-summary skill's worklogs[].id, or from the id a prior jira-worklog call returned.

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

State exactly what you're about to change (old vs. new duration/description/date) 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.

--date accepts the same formats as jira-worklog's --date (relative, ISO date, or ISO datetime) -- resolve relative day-names ("last Tuesday") to an actual calendar date yourself first.

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

Not sure whether the request is a new log, a fix to an existing entry, or a deletion? Use jira-log instead -- it routes to whichever of jira-worklog/jira-worklog-edit/jira-worklog-delete fits.

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

---name: jira-worklog-editdescription: Updates an existing Jira worklog entry's duration, description, or date. Use for "fix that worklog", "I logged the wrong date, change it to Tuesday", "change the description on that time log". This is a write operation gated behind explicit user confirmation.---# Jira: Worklog Edit**Write, gated.** Run from this skill's directory:```bashpython3 ../jira/scripts/jira_tool.py worklog_edit --issue_key PAY-123 --worklog_id 28459 \ [--duration 2h] [--description "..."] [--date 2026-07-20] --confirm```(First-time setup, once per environment: `pip install -r ../jira/requirements.txt`.)`--issue_key` and `--worklog_id` are required; at least one of`--duration`/`--description`/`--date` must also be given (omitted fieldsare left unchanged). Find `--worklog_id` via the `jira-issue-summary`skill's `worklogs[].id`, or from the id a prior `jira-worklog` callreturned.This refuses to execute unless run with `--confirm` (enforced in code,not just prompted). Unless `JIRA_AUTO_CONFIRM_WRITES=true` is set:1. State exactly what you're about to change (old vs. new duration/description/date) 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.`--date` accepts the same formats as `jira-worklog`'s `--date` (relative,ISO date, or ISO datetime) -- resolve relative day-names ("last Tuesday")to an actual calendar date yourself first.If the result contains `"error"`, tell the user what went wrong inplain language instead of retrying silently or fabricating a result.Not sure whether the request is a new log, a fix to an existing entry,or a deletion? Use `jira-log` instead -- it routes to whichever of`jira-worklog`/`jira-worklog-edit`/`jira-worklog-delete` fits.See `../jira/README.md` for architecture details and the fullenvironment-variable table.

Frequently asked questions