Home / alexander-danilenko / cortex-claude-code-plugins · GitHub

report-comment SKILL.md skillA

report-comment from alexander-danilenko/cortex-claude-code-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add alexander-danilenko/cortex-claude-code-plugins/report-comment@git:20261013.ecfffa1

Pins git:20261013.ecfffa1 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: alexander-danilenko/cortex-claude-code-plugins
Path: plugins/engineering/cortex-jira/skills/report-comment/SKILL.md
Versions recorded: 1
Latest version: git:20261013.ecfffa1, committed Oct 13, 2026
Size: 6,488 bytes
Repository stars: 17
License: MIT

Turn the git commits for a Jira ticket into a short, business-friendly implementation report and save it as local markdown. Use when the user wants to report finished work on a Jira ticket: a Jira report, update, or comment, a summary of their commits or changes for the ticket, or a note telling PM/QA what shipped.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Jira Report Comment

Generate a short Jira comment describing what shipped on a ticket, and save it as a local markdown file.

The reader — a PM, QA engineer, or architect — already has the ticket open. Every sentence that paraphrases the ticket back at them is a sentence they skip, and after two of those they stop reading the whole comment. So the comment carries only what the ticket cannot: what actually shipped, and what someone downstream now has to do differently.

By default that is one summary paragraph. Bug fixes add a Root Cause. Verify and Deploy sections appear only when the diff gives a concrete reason.

## Step 1 — Resolve the issue key

In order: the key the user gave you; otherwise the first `[A-Z]+-[0-9]+` match in `git branch --show-current`; otherwise ask.

Confirm before continuing: "I detected **CX-4328** from your branch. Use this issue key?"

Then reserve the output file, and write to this same path for the rest of the session — re-running the skill for the same issue updates the file rather than adding another:

```bash
mkdir -p docs/jira-reports
touch "docs/jira-reports/$(date +%Y-%m-%d-%H%M%S)-<ISSUE_KEY>.md"
```

## Step 2 — Fetch the ticket
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add alexander-danilenko/cortex-claude-code-plugins/report-comment@sha256:ba14321f239baee0

The line at the top of this page pins the label git:20261013.ecfffa1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_mviglbyedregukqu.svg)](https://markdownregistry.com/a/art_mviglbyedregukqu)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Oct 13, 2026.

version	committed	commit	size	audit
git:20261013.ecfffa1 latest	2026-10-13	ecfffa1	6,488 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (6488 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

alexander-danilenko/cortex-claude-code-plugins · 17 stars · license MIT · pushed 2026-10-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_mviglbyedregukqu
GET https://markdownregistry.com/api/v1/resolve?ref=alexander-danilenko/cortex-claude-code-plugins/report-comment
GET https://markdownregistry.com/api/v1/blob/ba14321f239baee03bc2f0e6d7f3cb54b44285d52305f1b681e58eb8c70bb762

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from alexander-danilenko/cortex-claude-code-plugins

CLAUDE.md CLAUDE.md file

alexander-danilenko/cortex-claude-code-plugins · CLAUDE.md

git:20261013.35be08e · audit A · 17 stars

answer-buzzkill SKILL.md skill

alexander-danilenko/cortex-claude-code-plugins · plugins/common/cortex-communication/skills/answer-buzzkill/SKILL.md · Write a short, fact-checked reply that answers a colleague's question in one meaning only, ready to copy and paste. The…