hive.terminal-tools-troubleshooting

仓库创建 2026年1月12日最近提交 1 个月前SkillHot 收录 20 天前

▸ 精选理由

快速定位常见终端异常，帮助高效排错并恢复流程。

这个 Skill 做什么

提供诊断步骤与处方，用于解决终端工具调用返回异常或输出缺失的情况。

提供终端工具异常输出的排查流程：针对 stdout 为空但应该有输出、exit_code 为 null、output_handle 过期、"too many PTYs" 等奇怪现象给出诊断步骤。什么时候用：terminal-tools 返回结果异常或语义状态和退出码不一致时调用它来定位原因。特点是按症状给处方式的检测项和解决办法，专治罕见或边缘故障，而不是常规成功路径。

▸ 展开 SKILL.md 英文原文

Read when a terminal-tools call returned something surprising — empty stdout despite no error, exit_code is null, output_handle came back expired, "too many jobs" / "session busy" / "too many PTYs", warning was set unexpectedly, semantic_status disagrees with exit_code. Diagnostic recipes only — load on demand. Don't preload; the foundational skill covers the happy path.

开发编程故障排查诊断日志通用

1.1w

Stars

5.7k

Forks

仓库内 Skill

+132

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/aden-hive/hive/main/core/framework/skills/_preset_skills/terminal-tools-troubleshooting/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/aden-hive/hive/main/core/framework/skills/_preset_skills/terminal-tools-troubleshooting/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Troubleshooting terminal-tools

Recipes for surprising results. Match the symptom to the section.

## Empty `stdout` despite the command "should have" produced output

Possible causes:
1. Output went to **stderr** instead. Check `stderr` in the envelope (or use `merge_stderr=True` for jobs).
2. Output was **fully truncated** because `max_output_kb` is too small. Check `stdout_truncated_bytes > 0`. Bump `max_output_kb` or paginate via `output_handle`.
3. Command produced no output (correct, just unexpected — `silent` flags, no matches).
4. Pipeline issue: the last stage of a pipe ran but stdout went elsewhere (`> /dev/null`, redirected via `2>&1`).
5. Process is buffering its output and did

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有