总评论
- 作者仓库星标 21
- 许可证 MIT
- 作者仓库 ttal-cli
- 领域
- 工程开发
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 94 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tta-lab · MIT
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# 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
章节与文件索引
按说明文件中的顺序排列。
命令
分诊模式
LGTM之后
规则
文件/命令 -> ttal comment list · ttal comment get <round> · ttal go <uuid> · ttal comment lgtm · ttal comment add
内容校验值 -> 44f669f257e5
当前原文的自动摘译,尚未人工审校。
命令
对于多行报告,请使用heredoc:
分诊模式
当收到带有调查结果的审核评论时:阅读评论:
ttal comment list,然后ttal comment get <round>评估每个发现:已修复/不适用/剩余 修复需要修复的内容 发布结构化分类更新:LGTM之后
当审阅者发布 LGTM 并且没有剩余的阻塞问题时:运行
ttal go <uuid>来推进管道(审阅者使用ttal comment lgtm自动设置标签) 您不需要发布任何内容 - 管道在 LGTM 标签上推进规则
始终通过
ttal comment add发布 - 永远不会仅内联输出结果 对任何超过一行的报告使用heredoc 审阅者:批准后始终调用ttal comment lgtm- 这设置了正确的管道标签 编码者:收到LGTM后,运行ttal go <uuid>以完成