comment SKILL.md skillB
comment from mulhamna/jira-commands is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mulhamna/jira-commands/comment@git:20261029.f79e226Pins git:20261029.f79e226 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mulhamna/jira-commands
- Path
plugin/skills/comment/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261029.f79e226, committed Oct 29, 2026
- First version recorded
- Apr 21, 2026
- Size
- 1,045 bytes
- Repository stars
- 54
- License
- a license file GitHub does not identify
Manage Jira issue comments with jirac, including listing existing comments and adding a new Markdown comment to an issue.
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
Manage Jira comments using `jirac`. Steps: 1. Check that `jirac` is available by running `jirac --version`. If it is missing, tell the user to install it with `cargo install jira-commands`. 2. Determine whether the user wants to list comments or add a comment. For listing comments: - extract the issue key - run `jirac issue comment <ISSUE-KEY> list` For adding a comment: - extract the issue key - extract the comment body - run `jirac issue comment <ISSUE-KEY> add --body '<COMMENT>'` - if the comment is long or already in a file, use `--file <FILE>` instead 3. Show the result clearly. Examples: - "show comments on PROJ-123" → `jirac issue comment PROJ-123 list` - "add a comment to PROJ-123 saying QA verified this" → `jirac issue comment PROJ-123 add --body 'QA verified this'` - "comment on PROJ-456 with the contents of note.md" → `jirac issue comment PROJ-456 add --file note.md`
Read the whole file at its exact version.
How to install
mdr add mulhamna/jira-commands/comment@sha256:9b6775affdb1b259The line at the top of this page pins the label git:20261029.f79e226, 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.
[](https://markdownregistry.com/a/art_ctebe7wvbbpyf577)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Apr 21, 2026 and Oct 29, 2026, about one every 191 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261029.f79e226 latest | 2026-10-29 | f79e226 | 1,045 B | B | view · diff |
| git:20260421.511ec27 | 2026-04-21 | 511ec27 | 1,045 B | B | view |
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1045 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
mulhamna/jira-commands · 54 stars · license a license file GitHub does not identify · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ctebe7wvbbpyf577 GET https://markdownregistry.com/api/v1/resolve?ref=mulhamna/jira-commands/comment GET https://markdownregistry.com/api/v1/blob/9b6775affdb1b259f410f83e2d81ed8d037d433ba0959df030fd10ba244aea4d
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.