jira-report-comment
Jira Report Comment
Generate a short Jira comment (60-100 words) describing what shipped on a ticket, and save it as a local markdown file.
Announce at start: "Using the jira-report-comment skill to generate an implementation report."
What This Skill Produces
The reader is a PM, QA engineer, or architect who already has the Jira ticket open. They do not need a recap of the ticket. They need:
- The summary - what shipped, in one or two sentences, framed as outcome. (Always present.)
- Root cause - why the problem existed and the approach taken to fix it. (Present when the ticket fixes an existing problem.)
- Verify - any non-obvious test path the ticket does not call out. (Usually omitted.)
- Deploy - any non-routine deploy step. (Usually omitted.)
Default output:
- Feature work: summary only.
- Bug fix: summary + Root Cause.
More from alexander-danilenko/cortex-ai-skills
humanize-text
Remove signs of AI-generated writing from text. Use after drafting to make copy sound more natural and human-written. Based on Wikipedia's "Signs of AI writing" guide.
4react
Apply these opinionated React conventions when writing React 18+ or 19 components: hooks patterns, Server Components, Suspense boundaries, state management, performance memoization, React 19 features (use, form actions).
4csharp
Apply these opinionated C# conventions when writing C#/.NET 8+ code: modern C# 12 (records, primary constructors, pattern matching), ASP.NET Core minimal and controller APIs, Blazor, Entity Framework Core, async patterns, CQRS with MediatR.
4python
Apply these opinionated Python 3.11+ conventions when writing Python in this codebase: type hints with mypy, async/await, pytest fixtures, dataclasses, Poetry packaging, production patterns.
4testing
Apply these opinionated testing conventions when writing tests or test strategies: three modes (functional, performance, security), unit/integration/E2E patterns, coverage analysis, automation frameworks, defect tracking, accessibility and usability.
4nestjs
Apply these opinionated NestJS conventions when writing NestJS backends: module structure, dependency injection, controllers and services, DTOs with class-validator, guards/interceptors/pipes, JWT authentication, TypeORM/Prisma.
4