jira-standup-auditor

Generates async daily standup updates by correlating Jira activity with local Git telemetry.

2|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/Gamaroff/agent-skills --skill jira-standup-auditor-gamaroff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-standup-auditor
Source: https://github.com/Gamaroff/agent-skills/tree/main/skills/jira-standup-auditor
Command: npx skills add https://github.com/Gamaroff/agent-skills --skill jira-standup-auditor-gamaroff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, jq, git, and includes scripts (resource) and references (resource) components.

What problem does it solve? Writing daily standup updates from memory is inaccurate and time-consuming. This Skill audits your actual Jira issue activity and local Git commits to compile a precise, factual async standup summary covering recent work, today's focus, and blockers. ## Core Features & Use Cases - Jira Activity Audit: Fetches issues assigned to or reported by you via the Jira Cloud REST API, including changelog history filtered to your accountId and blocked-by links. - Git Telemetry Extraction: Captures your active branch, commits from the last 48 hours authored by you, and uncommitted work-in-progress files. - Correlated Standup Report: Matches ticket keys found in branch names and commit messages to Jira issues, then formats a structured Markdown update with Yesterday/Recent Work, Today's Focus, and Blockers sections. - Use Case: On Monday morning, ask for your standup prep and receive a report that automatically covers Friday's work (the lookback window extends to -3d on Mondays), flags stalled in-progress issues, and lists blockers with their statuses. ## Quick Start Ask the agent to prepare my daily standup update based on my recent Jira and Git activity.

Frequently Asked Questions about jira-standup-auditor

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

FAQPage Schema
How do I generate a daily standup update from Jira and Git?▼

Run the Jira activity script to fetch your recently updated issues with changelog history, then run the Git activity script to capture your branch, last-48h commits, and uncommitted files. The Skill correlates ticket keys between both sources and formats a Markdown standup report.

What Jira API endpoint does standup reporting use?▼

It uses POST /rest/api/3/search/jql with nextPageToken pagination, since Atlassian retired the legacy GET /rest/api/3/search endpoint in May 2025. It also calls GET /rest/api/3/myself to resolve your accountId for changelog filtering.

What environment variables are required for Jira API access?▼

Three variables are required: JIRA_URL (your tenant host like your-tenant.atlassian.net), JIRA_USER_EMAIL (your Atlassian account email), and JIRA_API_TOKEN (created at id.atlassian.com). The token only needs read access for myself and issue search.

Does the Jira standup skill work with Jira Server or Data Center?▼

No, it targets Jira Cloud only. The search/jql endpoint is available on Cloud tenants (*.atlassian.net); Server/DC URLs will return HTTP 404 or 410 errors on search requests.

Why is my recentCommits list empty with a warning?▼

This happens when git config user.email is not set in the local repository, so the commit filter cannot match your authorship. Set it with git config user.email [email protected], either locally or with --global.

How far back does the standup report look for activity?▼

The default lookback window is -1d, automatically extended to -3d on Mondays so Friday's work is captured. You can override it by passing a JQL relative date expression like -2d as the first script argument.