Saucebox Registry
← Browse

@mulhamna/bulk-comment

B

Add the same Markdown comment to multiple Jira issues with jirac, either by JQL query or explicit issue keys

skillclaude

Install

agr install @mulhamna/bulk-comment --target claude

Writes 1 file into .claude/skills/, pinned to git-ab8fd2d6.

  • .claude/skills/bulk-comment/SKILL.md

Document

description: Add the same Markdown comment to multiple Jira issues with jirac, either by JQL query or explicit issue keys

Bulk comment on Jira issues 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. Extract from the user's request:
    • a JQL filter, or an explicit issue-key list
    • the Markdown comment body
    • whether to skip confirmation
  3. Run one of:
    • jirac issue bulk-comment --jql '<JQL>' --body '<COMMENT>' [--force]
    • jirac issue bulk-comment --keys PROJ-1 PROJ-2 --body '<COMMENT>' [--force]
    • use --file <PATH> instead of --body when the comment lives in a file
  4. Confirm how many issues were updated and report any failures.

Examples:

  • "comment on all in-progress PROJ issues that QA started verification" → jirac issue bulk-comment --jql 'project = PROJ AND status = "In Progress"' --body 'QA started verification'
  • "post this note on PROJ-1 and PROJ-2" → jirac issue bulk-comment --keys PROJ-1 PROJ-2 --body 'Please add your update before standup'

Trustgrade B

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • warnLicenseno SPDX license detected

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-ab8fd2d668ed2026-07-31