jira-work-report

To generate a Jira report automatically, the Skill derives the issue key from your current git branch, reads recent commits to populate a structured template, and posts the completed implementation report as a Jira comment.

Yes, you can post commit summaries as a Jira comment by having the agent read your branch's commit evidence, fill out a predefined work report template, and publish it directly to the derived Jira issue via MCP Jira tools.

Deriving a Jira issue key from a git branch works by applying project key rules to the branch name, with optional overrides, to automatically identify the target Jira issue for the report publication.

Before generating Jira work reports, you need a valid Jira configuration, a current git branch with commits, and a Jira work report template; the Skill validates the Jira setup and reads the template to build the narrative.

Yes, this Jira reporting automation works with custom project key rules, using them to accurately derive the Jira issue key from the current branch name while also supporting optional overrides for specific cases.

If your Jira configuration is invalid, the Skill validates the setup before processing and will prevent the derivation of the issue key from the branch, stopping the report generation and comment publication from failing silently.