Skip to content
Agentmart
Submit a tool

jira-comment

Use to post a comment on a Jira issue without moving it — a finding, a question for the reporter, a status note, the path of an artifact.

Skill by agentchieflou

IndexedMIT★ 1
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/agentchieflou-jira-comment

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use to post a comment on a Jira issue without moving it — a finding, a question for the reporter, a status note, the path of an artifact. Dry-run first, one comment, never a transition.

Use cases: productivity

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/jira-comment

What's inside

Skill name
jira-comment
Description
Use to post a comment on a Jira issue without moving it — a finding, a question for the reporter, a status note, the path of an artifact. Dry-run first, one comment, never a transition.
License
MIT
Instructions
10 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Comment on a Jira issue (never move it)

A comment is a write to a system of record (AGENTS.md rule 8): dry-run, read `"ok"`, then post. It is not a transition -- moving the issue is `jira-transition`'s, and a comment that *asks* the reporter something is still a comment, not a stop.

1. `state.active_ticket`, or the key the user named, is required. Missing → `session-bootstrap`. STOP.
2. Write the body to `.agent/out/<KEY>-comment.md`, ≤ 12 lines, plain text (Cloud renders it as ADF; no Markdown tables). Say what was found or asked, and name every `.agent/out/` path the reader will want. Never paste rows: more than 10 rows is a findings file, and the comment names it.
3. Dry run: `ad-jira comment <KEY> --body-file .agent/out/<KEY>-comment.md --dry-run`. Read `"ok"`. `refused:` → the `hint` names the fix (`not_found`, `jira auth`); `friction-log` type `tool-error`. STOP.
4. Post: the same command without `--dry-run`. In a fleet it waits on the approval gate; `approval_timeout` or `approval_denied` → `friction-log` type `missing-info` quoting the `approval` id. Do not retry.
5. Print the comment id and the key in one line. `state-update` with `--artifact .agent/out/<KEY>-comment.md="comment posted on <KEY>"`. Return to `router`.

From agentchieflou/this-next-please, MIT.

More from agentchieflou/this-next-please

Signals

Stars
1
Forks
0
Open issues
61
Last commit (this folder)
Oct 3, 2026 (26 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/agentchieflou/this-next-please
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from agentchieflou

Cite this page

jira-comment skill. Agent Mart. https://agentmart.dev/skills/agentchieflou-jira-comment (last updated 2026-10-24)