jira-worklog

Create, link, and update Jira issues with approval-gated writes and local records.

Updated Jul 24, 2026
One-click install
npx skills add https://github.com/eklyukin/my-ai-config --skill jira-worklog-eklyukin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-worklog
Source: https://github.com/eklyukin/my-ai-config/tree/main/skills/jira-worklog
Command: npx skills add https://github.com/eklyukin/my-ai-config --skill jira-worklog-eklyukin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping Jira synchronized with actual repository work is error-prone: issues get duplicated, comments get posted without review, and local plans drift from remote state. This Skill enforces a preview-and-approval workflow for every Jira write and persists a local record of every touched issue. ## Core Features & Use Cases - Publish or Link Plans: Search Jira for duplicates, link confirmed implementation plans to existing issues, or create new issues in the default IEO project after explicit approval. - Progress and Finish Workflows: Draft evidence-based progress comments, add missing PR/MR remote links before transitions, and reconcile plans with Jira state. - Mandatory Local Records: Persist every touched issue under .context/sources/jira/ with provenance, status, and relationships, and coordinate Jira-key branch naming conventions. - Use Case: After finishing a feature on branch IEO-121, ask the assistant to post a progress comment and transition the issue; it will preview the comment, verify all PR links exist as native Jira remote links, and write only after your confirmation. ## Quick Start Ask the assistant to link the current implementation plan to a Jira issue or create a new IEO issue and show the preview before writing.

Frequently Asked Questions about jira-worklog

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

FAQPage Schema
How do I create a Jira issue from an implementation plan?▼

The Skill reads the confirmed plan, searches Jira for duplicates, and prepares a creation preview with project, issue type, summary, and description. It creates the issue only after you explicitly approve the preview, then updates the plan's Jira section.

How to post a Jira progress comment from Git work?▼

Progress comments are derived from observable evidence: the linked plan, Git diff and commits, test results, and PR state. The comment draft is shown for confirmation before posting, and the local Jira source record is refreshed afterward.

Does this Skill work without an Atlassian MCP connection?▼

Yes, but only partially. Without a connected Jira or Atlassian MCP, it prepares the same previews and explains what connection is missing; it never pretends a remote write succeeded.

Can Jira issues be created or transitioned without approval?▼

No. Every Jira write, including creation, edits, comments, transitions, and remote-link additions, requires a fresh explicit approval after a complete preview. Approval of a plan or prior action is never reused.

Why must a Jira issue have remote links before closing?▼

The Skill requires every relevant PR or MR URL to exist as a native Jira remote link before a resolved or closed transition. Mentioning links in comments is insufficient, ensuring Jira accurately reflects delivered code.

What branch naming convention does the Jira workflow use?▼

Branches are named exactly after their Jira key, such as IEO-121, with no prefixes like feat/ or fix/. Issue branches within an epic are created from and target the epic branch.