Skill

jira-activity-summary

This skill MUST be used when the user asks to summarize their own Jira activity, what they personally worked on, or what they did in Jira over a time period. Trigger phrases include "summarize my jira activity", "what did I do in jira", "show my jira activity", "my activity in mbc", "what did I work on", "jira activity report", or any request combining a personal possessive ("my") with a Jira project and a time period (today, yesterday, this week, last week, this month). This skill is specifically for personal activity summaries — NOT sprint reports, NOT backlog listings, NOT issue searches. Examples: "summarize my jira activity in mbc yesterday", "what did I work on in mbc this week", "show my mbc activity last week".

npx claudepluginhub ericfisherdev/claude-plugins --plugin jira-tools

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Generates a structured activity report showing status changes on your assigned tickets and comment activity during a given time period.

Supporting Assets

scripts/jira_activity.py

SKILL.md

Similar Skills

finishing-a-development-branch

174.6k

Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.

superpowers

systematic-debugging

174.6k

Guides root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.

10 files

superpowers

writing-plans

174.6k

Writes implementation plans from specs for multi-step tasks, mapping files and breaking into TDD bite-sized steps before coding.

1 file

superpowers

Stats

Parent Repo Stars1

Parent Repo Forks0

Last CommitMar 4, 2026

Actions

View Source View Plugin View on GitHub View README

Jira Activity Summary

Generates a structured activity report showing status changes on your assigned tickets and comment activity during a given time period.

How to use

Extract the project key (e.g., MBC) and time period from the user's request.
Map the time period to one of the script's accepted values:
- "today" → today
- "yesterday" → yesterday
- "this week" → this_week
- "last week" → last_week
- "this month" → this_month
If the project key is missing, ask the user for it before proceeding.
Run the script and display the output directly — no reformatting needed.

Running the script

python <skill-dir>/scripts/jira_activity.py --project <PROJECT_KEY> --period <period>

Examples:

python scripts/jira_activity.py --project MBC --period yesterday
python scripts/jira_activity.py --project MBC --period this_week
python scripts/jira_activity.py --project MBC --period last_week --max-issues 200

--max-issues defaults to 100. Increase it if the user reports missing activity on busy weeks/months.

What the report covers

Ticket changes — status transitions on tickets assigned to you during the period. If a ticket moved through multiple states, the full chain is shown (e.g., moved from To Do to In Progress to Done).

Comments — three types, deduped so no comment appears twice:

Comments you left on any ticket in the project
Comments by others on tickets assigned to you
Comments that @mention you (by accountId in Atlassian Document Format)

Environment variables required

JIRA_BASE_URL    https://yoursite.atlassian.net
JIRA_EMAIL       your-email@example.com
JIRA_API_TOKEN   your-api-token

These should already be configured if the user has other jira-tools skills working.

Output format

The script prints markdown matching this template:

# Jira Activity for 03/03/2026

## Ticket changes
MBC-1234 moved from To Do to In Progress
MBC-1235 moved from To Do to In Progress to Done

## Comments
### Left a comment on MBC-2345 (assigned to John Doe):
- "comment text here"

### John Doe commented on your ticket MBC-1235:
- "This looks good"

### Jane Smith mentioned you in a comment on MBC-2567:
- "comment text here"