work-review

Correlate git commits with Jira tickets and generate a structured work-review report.

2|1|Updated Jan 26, 2026

Search Tags:#git #analysis #review #jira #report #epic

Ready to run

npx skills add https://github.com/TrevorEdris/fellowship-of-the-workflows --skill work-review-trevoredris

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: work-review
Source: https://github.com/TrevorEdris/fellowship-of-the-workflows/tree/main/workflows/skills/work-review
Command: npx skills add https://github.com/TrevorEdris/fellowship-of-the-workflows --skill work-review-trevoredris

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the process of correlating Jira tickets with Git commits to generate a concise, review-ready summary of a team or individual's work over a defined period.

Core Features & Use Cases

Correlates commits to Jira tickets using commit messages and optional Atlassian MCP integration for enriched ticket data.
Groups work by epic, identifies tickets without an epic association, analyzes pull request patterns, and produces a structured review report.
Supports self-reviews, peer reviews, sprint retrospectives, and performance discussions across multiple repositories.

Quick Start

Provide the author email or name and a date range to generate a Work Review. Example: "Review [email protected] commits from 2026-01-01 to 2026-01-31".

Frequently Asked Questions about work-review

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

FAQPage Schema

How do I generate a work review from Jira tickets and git commits?▼

To generate a work review, provide an author email or name and a date range. The Skill correlates git commits with Jira tickets using commit messages and produces a structured review report.

Can I use Atlassian MCP integration to enrich Jira ticket data in a sprint retrospective?▼

Yes, Atlassian MCP integration is optionally supported to enrich Jira ticket metadata for sprint retrospectives. The Skill uses this data to group work by epic and analyze pull request patterns.

Does the work review report support multiple repositories for performance discussions?▼

Yes, the work review report supports performance discussions across multiple repositories. It correlates git history and Jira ticket references to summarize an individual or team's work over a defined period.

What do I need to correlate git commits with Jira epics for a peer review?▼

You need access to git history and Jira ticket references in commit messages to correlate commits with epics for a peer review. Optional MCP integration provides enriched ticket metadata for deeper analysis.

How does the Skill handle tickets without an epic association in the review report?▼

The Skill explicitly identifies and groups tickets without an epic association in the structured review report. This ensures unassociated work is visible during self-reviews and sprint retrospectives.

Are there limitations when analyzing pull request patterns across multiple repositories?▼

The primary limitation is the reliance on Jira ticket references in commit messages; without them, correlation fails. Optional MCP integration is required if you need enriched Atlassian ticket metadata for the analysis.