From cortex
Generates business-friendly Jira ticket reports by summarizing git commits against issue context using Atlassian MCP and saves as dated markdown file in docs/jira-reports.
npx claudepluginhub alexander-danilenko/cortex-ai-skills --plugin cortexThis skill is limited to using the following tools:
Generate a non-technical, business-focused summary of git changes for a Jira issue and save it as a markdown report.
Fetches JIRA issue by key or search, distills title/description/acceptance criteria/comments into structured task, analyzes codebase for gaps/risks, optionally enriches JIRA.
Generates timestamped Markdown previews of Jira issues from track plans, mapping tracks to epics, phases to stories, tasks to sub-tasks, with git metadata for review before creation.
Generates polished standalone HTML reports summarizing bug fixes, features, refactoring, investigations, or architectural decisions. Auto-opens in browser after tickets or debug sessions.
Share bugs, ideas, or general feedback.
Generate a non-technical, business-focused summary of git changes for a Jira issue and save it as a markdown report.
Announce at start: "Using the jira-report-comment skill to generate an implementation report."
Determine the Jira issue key using this priority:
If the user provided an issue key (e.g., "CX-4328"), use it directly.
Otherwise, extract from the current branch name:
git branch --show-current
Parse the ticket ID using the pattern [A-Z]+-[0-9]+ (e.g., feature/ABC-1234-description yields ABC-1234).
If no key can be determined, ask the user.
Always confirm the resolved key with the user before proceeding: "I detected CX-4328 from your branch. Use this issue key?"
Immediately after confirming the issue key, reserve the output file. This locks the filename for the entire session — all subsequent writes go to this same file.
mkdir -p docs/jira-reports
touch "docs/jira-reports/$(date +%Y-%m-%d)-$(date +%s)-<ISSUE_KEY>.md"
Store the full file path in conversation context (e.g., docs/jira-reports/2026-03-27-1743091200-ABC-123.md). This is the only file you will write to for the rest of this session. If the skill is invoked again in the same session for the same issue, reuse this path — do not create a new file.
Retrieve the issue to understand what was requested. Try the Atlassian MCP tool first:
mcp__atlassian__getJiraIssue
issueIdOrKey: "<ISSUE_KEY>"
If the MCP tool is unavailable or fails, ask the user to provide the issue context manually: "Atlassian MCP is not available. Please paste the issue text (title, description, acceptance criteria) or provide an XML export."
Extract and note:
This context is essential. The report must map code changes back to what was actually requested in the ticket.
Find all commits referencing the issue key:
git log --grep="<ISSUE_KEY>" --format="%H %s" --reverse
If no commits found, widen the search:
git log --all --grep="<ISSUE_KEY>" --format="%H %s" --reverse
If still no commits, fall back to diffing the current branch against its base:
git merge-base HEAD main
git diff $(git merge-base HEAD main)..HEAD --stat
git diff $(git merge-base HEAD main)..HEAD
Try main, then master, then develop as the base branch. If no meaningful diff is found, inform the user and stop.
For the aggregate diff across all found commits (first commit's parent to last commit):
git diff <FIRST_COMMIT>^..<LAST_COMMIT> --stat
git diff <FIRST_COMMIT>^..<LAST_COMMIT>
If the first commit is the initial repository commit (no parent), use git diff $(git hash-object -t tree /dev/null)..<LAST_COMMIT> instead.
This shows the net result across all commits, not incremental progress. The aggregate diff reveals what actually changed, while individual commits often contain scaffolding and refinements.
If the diff is very large (50+ files), focus on the stat summary and read only the most significant files. Configuration files, test files, and migration files often reveal intent better than implementation details.
Load the reference template:
references/report-template.md — read this now for the output structureAnalyze the diffs with a business lens. Map every code change to a user-facing or system-facing outcome.
references/formatting-rules.md and follow all rules strictlyhumanize-text skill is available, run the final report through it before presenting to the userWrite the report content to the reserved file path (overwriting the empty placeholder):
Write tool -> file_path: <RESERVED_FILE_PATH>
content: <REPORT_CONTENT>
Present the report to the user in the conversation and confirm: "Report saved to <RESERVED_FILE_PATH>."
If the user requests changes, revise and overwrite the same file again.
references/report-template.md — Structured template for the Jira comment output. Load when generating the report in Step 4.references/formatting-rules.md — Tone, style, and formatting constraints for the report. Load alongside the template in Step 4.