Help us improve
Share bugs, ideas, or general feedback.
From work-summary
This skill should be used when the user asks to "generate a client summary", "create a client-friendly summary", "write QA steps from my changes", "summarize changes for stakeholders", or needs a non-technical summary of code changes with QA steps and testing checklists. Can be used standalone or as part of the work-summary workflow.
npx claudepluginhub joshuarweaver/cascade-code-general-misc-3 --plugin oraseslabs-orases-claude-code-marketplaceHow this skill is triggered — by the user, by Claude, or both
Slash command
/work-summary:client-summary-generatorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate a client-friendly summary from code changes and Jira ticket context. This summary
Generates short Jira comments from git commits summarizing shipped features or bug fixes with root cause analysis. Fetches issue details via Atlassian MCP and saves as local markdown report.
Writes structured pull request descriptions by analyzing git diffs and code changes. Supports customizable templates and ticket context.
Summarizes recent changes from git history, meeting notes, sprint progress, documents, or logs for context recovery, handoffs, and sprint reviews.
Share bugs, ideas, or general feedback.
Generate a client-friendly summary from code changes and Jira ticket context. This summary targets non-technical stakeholders — project managers, QA teams, and clients. Every claim must be grounded in actual code changes or ticket data.
This skill requires:
When invoked from the work-summary:work-summary-generator skill, these are provided from
earlier steps. When used standalone, gather them first.
Check for template overrides in settings. If a client_summary_template path is defined
in the work-summary settings file (.claude/work-summary.local.md, .claude/work-summary.md,
or ~/.claude/work-summary.md), load that template instead of the built-in default.
If not already available from an earlier workflow step:
git diff, git log) for the relevant branchProduce these sections (omit any that do not apply):
Refer to the template at ${CLAUDE_PLUGIN_ROOT}/skills/client-summary-generator/templates/client-summary-template.md
for the complete Markdown structure. If a template override is configured in settings, use
that instead.
After generating, display the QA Steps and Testing Checklist as plain text output so the user
can read them. Then ask via AskUserQuestion:
${CLAUDE_PLUGIN_ROOT}/skills/client-summary-generator/templates/client-summary-template.md - Default Markdown structure for the client-friendly summary