edge-ic:update-jira

Synchronize Jira issues with daily TODO accomplishments via comments, worklogs, and status transitions.

7|15|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/openshift-eng/edge-tooling --skill edge-ic-update-jira
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edge-ic:update-jira
Source: https://github.com/openshift-eng/edge-tooling/tree/main/plugins/edge-ic/skills/update-jira
Command: npx skills add https://github.com/openshift-eng/edge-tooling --skill edge-ic-update-jira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents Jira issues from falling out of sync with real daily progress by turning today’s TODO accomplishments into accurate comments, status transitions, and worklogs.

Core Features & Use Cases

  • Reads today’s TODO file: Uses the daily markdown file at $HOME/.daily/YYYY/MM/YYYY-MM-DD.md to drive updates for only the current day.
  • Updates related Jira issues: Extracts ticket keys and accomplishment text, then applies comments, worklogs, and validated transitions.
  • Safety-first prompting: Prompts before making any changes to avoid unintended Jira modifications.

Quick Start

Ask the skill to read today’s TODO file and, with your confirmation, update each referenced Jira ticket with the appropriate comment, status transition, and worklog.

Frequently Asked Questions about edge-ic:update-jira

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

FAQPage Schema
How do I update Jira issues from a daily markdown TODO log?

To update Jira issues from a daily markdown TODO log, this skill reads your file at $HOME/.daily/YYYY/MM/YYYY-MM-DD.md, extracts ticket keys and accomplishment text, and applies comments, worklogs, and status transitions. You confirm each prompt before it modifies Jira.

What is the best way to sync Jira worklogs with daily engineering progress?

The best way to sync Jira worklogs with daily engineering progress is extracting completed TODO items and accomplishment text from your daily markdown file, then using MCP Jira tools to record worklogs and apply validated status transitions with safety-first prompting.

How do I automatically add accomplishment-based comments to Jira tickets?

You can automatically add accomplishment-based comments to Jira tickets by reading today's TODO markdown file to extract ticket keys and achievement text, then prompting for confirmation before applying updates via MCP Jira tools.

Can I use a markdown TODO file to apply validated status transitions in Jira?

Yes, you can use a markdown TODO file to apply validated status transitions in Jira. The skill parses ticket keys from your daily file and uses MCP Jira tools to transition ticket statuses, prompting you before making any changes.

Do I need a specific file format to synchronize Jira issues with my TODO log?

Yes, you need a specific markdown file format at $HOME/.daily/YYYY/MM/YYYY-MM-DD.md. This daily TODO file must contain ticket keys and accomplishment text for the skill to extract and synchronize with Jira issues.

Will this skill modify my Jira tickets without confirmation?

No, this skill uses safety-first prompting and will not modify your Jira tickets without confirmation. It prompts you before making any changes to avoid unintended modifications to comments, worklogs, or status transitions.