ttal comment

Engineering Community

Skill notes

Commands

For multiline reports, use heredoc:

Triage Pattern

When receiving a review comment with findings: Read the comment: ttal comment list then ttal comment get <round> Assess each finding: Fixed / Not Applicable / Remaining Fix what needs fixing Post a structured triage update:

After LGTM

When a reviewer posts LGTM with no remaining blocking issues: Run ttal go <uuid> to advance the pipeline (reviewers use ttal comment lgtm which sets the tag automatically) You do NOT need to post anything — the pipeline advances on the lgtm tag

Rules

Always post via ttal comment add — never output findings inline only Use heredoc for any report longer than one line Reviewers: always call ttal comment lgtm after approving — this sets the correct pipeline tag Coders: after receiving LGTM, run ttal go <uuid> to finalize

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tta-lab · MIT
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# ttal-comment Skill

## Overview
ttal comment is the unified tool for posting and reading review comments in the pipeline. Use it for plan reviews, PR reviews, triage reports, and verdicts.

## Commands

```
ttal comment list                    # list all comments on current task
ttal comment get <round>             # read specific review round
ttal comment add "message"           # post comment (short messages)
ttal comment lgtm                    # approve current pipeline stage (reviewers only, auto-detects stage)
```

For multiline reports, use heredoc:
```
cat <<'REVIEW' | ttal comment add
## Review Findings
**Verdict:** Ready
REVIEW
```

## Triage Pattern

When receiving a review comment with findings:

1. Read the comment: `ttal comment list` then `ttal comment get <round>`
2. Assess each finding: Fixed / Not Applicable / Remaining
3. Fix what needs fixing
4. Post a structured triage update:

```
cat <<'TRIAGE' | ttal comment add
## Triage Report (Round N)

**Fixed:**
- Issue 1 — what was done
- Issue 2 — what was done

**Not Applicable:**
- Issue 3 — why it doesn't apply

**Remaining:**
- Issue 4 — why it's deferred (or still being worked)
TRIAGE
```

5. If no remaining blocking issues: run `ttal go <uuid>` to advance the pipeline

## After LGTM

When a reviewer posts LGTM with no remaining blocking issues:
- Run `ttal go <uuid>` to advance the pipeline (reviewers use `ttal comment lgtm` which sets the tag automatically)
- You do NOT need to post anything — the pipeline advances on the lgtm tag

## Rules

- Always post via `ttal comment add` — never output findings inline only
- Use heredoc for any report longer than one line
- Reviewers: always call `ttal comment lgtm` after approving — this sets the correct pipeline tag
- Coders: after receiving LGTM, run `ttal go <uuid>` to finalize

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.