Name: Jira Changelog Summary
Author: shady-robot

Jira Changelog Summary Skill

When to Use

When you have a list of Jira tickets with details and changelog data from other skills' script results.
To generate concise, business-friendly summaries of ticket changes.

Input: A JSON object where keys are ticket IDs (e.g., "SECTOOLING-XX") and values are objects with fields like "description", "title", and "acceptance_criteria". Changelog data is provided as results from other skills' scripts (e.g., API fetches or exports).
Process:
1. Parse the input ticket list.
2. For each ticket, retrieve or reference the changelog from the provided script results (assume it's passed as additional context or via tool output).
3. Summarize the changelog in 1-2 sentences (≤20 words total), focusing on user-friendly business language (e.g., highlighting key changes, impacts, or resolutions without technical jargon).
4. Ensure summaries are concise and actionable.

When you have a list of Jira tickets with details and changelog data from other skills' script results.
To generate concise, business-friendly summaries of ticket changes.

Input: A JSON object where keys are ticket IDs (e.g., "SECTOOLING-XX") and values are objects with fields like "description", "title", and "acceptance_criteria". Changelog data is provided as results from other skills' scripts (e.g., API fetches or exports).
Process:
1. Parse the input ticket list.
2. For each ticket, retrieve or reference the changelog from the provided script results (assume it's passed as additional context or via tool output).
3. Summarize the changelog in 1-2 sentences (≤20 words total), focusing on user-friendly business language (e.g., highlighting key changes, impacts, or resolutions without technical jargon).
4. Ensure summaries are concise and actionable.