jira-add-worklog

Derive Jira issue keys from Git branches and submit worklogs.

1|Updated Dec 9, 2024
One-click install
npx skills add https://github.com/hadenlabs/tasks --skill jira-add-worklog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-add-worklog
Source: https://github.com/hadenlabs/tasks/tree/main/.claude/skills/jira-add-worklog
Command: npx skills add https://github.com/hadenlabs/tasks --skill jira-add-worklog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates recording time against Jira issues by deriving the issue key from your Git branch and summarizing recent commits into a concise worklog description.

Core Features & Use Cases

  • Derives the Jira issue key from the current branch using a configured project key or a regex override, then logs time against that issue.
  • Validates Jira configuration by reading jasper.toml and ensuring issueTracking.provider = "jira".
  • Prompts for time spent in Jira-friendly formats (e.g., 30m, 2h) and builds a short, commit-based description for the worklog.
  • Works on feature/branch workflows and helps automate time tracking for development work.

Quick Start

Tell your agent to log a Jira worklog for the current branch with a time value and a concise commit-based description.

Frequently Asked Questions about jira-add-worklog

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

FAQPage Schema
How do I log Jira worklog time from a Git branch automatically?

You can log Jira time from a Git branch by using a skill that derives the Jira issue key from the branch name, reads the project key from jasper.toml, and submits a worklog entry with a commit-based summary to Jira.

What is the process for deriving a Jira issue key from a feature branch?

Deriving a Jira issue key from a feature branch involves reading the configured project key from jasper.toml or applying a regex override to extract the matching issue key directly from the branch name.

Does logging Jira worklogs from a branch require a jasper.toml configuration file?

Yes, logging Jira worklogs from a branch requires a jasper.toml file. The skill validates this file to ensure the issue tracking provider is set to "jira" and reads the projectKey needed to derive the issue.

How do I summarize Git commits into a Jira worklog description?

To summarize Git commits into a Jira worklog description, the skill reads your recent commit context from the current branch and builds a concise summary that is submitted as the worklog comment to Jira.

What time formats are supported when logging time against a Jira issue?

When logging time against a Jira issue, the skill prompts for time spent using Jira-friendly formats such as 30m or 2h, passing this value directly as the timeSpent parameter in the Jira worklog submission.

Can I override the default branch regex used to derive the Jira issue key?

Yes, you can override the default branch regex used to derive the Jira issue key. The skill allows a regex override to extract the correct issue key when the standard project key derivation does not fit your naming convention.