issue-tracker-comment

Files (1)

• SKILL.md

SKILL.md (first lines)

# Issue Tracker Comment

Shared reference for every phase agent's own "Issue Tracker Comment (optional)" step, invoked with two parameters the calling agent states inline: `{output_file}` (the `.kairos/<feature_folder>/` file to post) and `{title}` (the Markdown heading used as the comment's own title, e.g. `## Code Review`).

If the user provides an issue reference (Jira `PROJ-42`, GitLab/Bitbucket `#42`), post `{output_file}` as a comment on that issue once the human approves it at the phase's own HITL gate.

## Plain body

Most agents post the file with no extra heading — the tracker comment's own context (which pipeline run, which phase) is already clear from the issue thread.

**Jira** (`jira-cli`):
```bash
jira issue comment add PROJ-42 "$(cat .kairos/<feature_folder>/{output_file})"
```

**GitLab** (`glab`):
```bash
glab issue note <issue-id> --message "$(cat .kairos/<feature_folder>/{output_file})"
```

## Title-prefixed body

`pm-agent`, `architect-agent`'s implementer counterparts (`implementer-tdd-agent`, `implementer-coder-agent`), and `impact-assessment-agent` prefix `{title}` before the file content instead:

**Jira** (`jira-cli`):
```bash
jira issue comment add PROJ-42 "{title}\n\n$(cat .kairos/<feature_folder>/{output_file})"
```

**GitLab** (`glab`):
```bash
glab issue note <issue-id> --message "{title}\n\n$(cat .kairos/<feature_folder>/{output_file})"
```

## Extract body

`qa-plan-agent` posts a subset of its artifact rather than the file: its reader is a tester, and half of `05b-qa-plan.md` is pipeline bookkeeping that tester cannot act on. The agent's own step names which sections go in. In an orchestrated run the agent writes that body to `_qa-file.md` (the whole extract) and `_qa-comment.md` (the Core and a pointer line), and the orchestrator posts one of them after its gate, as the human chose (a plain body: `cat` that file, never `05b-qa-plan.md`). Standalone, the agent composes it inline — no `cat` of the artifact, and no second file written to hold the extract:

**GitLab** (`glab`):
```bash
glab issue note <issue-id> --message "$(cat <<'BODY'
{title}

<extract>
BODY
)"
```

**Jira** (`jira-cli`):
```bash
jira issue comment add PROJ-42 "$(cat <<'BODY'
{title}

<extract>
BODY
)"
```

A heredoc, not an inline string: the extract carries Markdown tables and backticks, and quoting those into a one-line argument is how a comment arrives mangled.

## Bitbucket (REST API)

Same shape for every agent regardless of plain/title-prefixed above:

```bash
curl -X POST "https://api.bitbucket.org/2.0/repositories/{workspace}/{repo}/issues/<id>/comments" \
  -u "${BITBUCKET_USER}:${BITBUCKET_TOKEN}" \
  -H "Content-Type: application/json" \
  -d "{\"content\":{\"raw\":\"{title}\"}}"
```

## No tracker CLI available

Never assume `jira`, `glab`, or `curl` is installed — corporate machines frequently have none of them, and an unguarded call fails in the middle of a phase gate. Before running any command above, check: `command -v jira`, `command -v glab`.

If none is present, or the command fails, **do not fail the phase** — the artifact is already durable on disk. Print the ready-to-paste comment body and the command the user can run later:

```
📋 Not posted automatically (<no tracker CLI found | post failed: <reason>>).
Paste this as a comment on <issue ref>:

<{title}, if this agent uses the title-prefixed form>

<content of .kairos/<feature_folder>/{output_file}>
```

Then continue. This applies to every agent below as well.

## No-Bash agents

`context-extractor-agent` and `documentation-agent` have no `Bash` tool (narrowed in v6.7.0 to match their stated contract). They cannot run the commands above themselves — extract `{output_file}`'s relevant section as the comment body and hand it, plus the matching command, to the user or orchestrator to run.

## Read-only agents

`security-reviewer-agent` and `impact-assessment-agent` have no `Write`/`Edit`/`Bash` at all (`tools: Read, Grep, Glob, AskUserQuestion`) — instruct the orchestrator to post on their behalf rather than running the command directly, same as their own Write-to-Project step.

From diego81b/kairos-agents-framework, AGPL-3.0.

More from diego81b/kairos-agents-framework