fable-understand

仓库创建 2026年7月5日最近提交 22 天前SkillHot 收录 22 天前
▸ 精选理由

能把抽象问题映射到具体实现并给出出处,便于代码审查与知识传递。

这个 Skill 做什么

基于实现证据解释代码库的行为、架构、引导和数据流。

从代码实现的证据出发解释系统如何工作,描述行为、架构、启动流程、数据流和集成接点,并在回答里给出引用和未解之处。适用于追踪调用路径、映射子系统或回答“这段代码怎么跑起来”的问题,不依赖过时文档或记忆。遇到大规模或高风险的理解任务,会启用 Codex 子代理并遵循执行合约以提高可靠性。

▸ 展开 SKILL.md 英文原文

Source-grounded codebase understanding for behavior, architecture, boot flow, data flow, integration wiring, or "how does this work" questions. Use when the user asks Codex to explain a system, trace a path, map a subsystem, or answer behavior questions with citations and unknowns.

开发编程代码理解行为追踪架构映射证据引用Codex
0
Stars
0
Forks
6
仓库内 Skill
+0
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/rhein1/fable5-codex/main/plugins/fable5-codex/skills/fable-understand/SKILL.md
或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/rhein1/fable5-codex/main/plugins/fable5-codex/skills/fable-understand/SKILL.md"
SKILL.MD 节选查看完整文件 ↗
# Fable Understand

Answer from implementation evidence, not memory or stale docs.

For ECF-style governed runs, use `../../references/ecf-run-contract.md`. For large or high-risk understanding tasks, use real Codex subagents when the runtime exposes a subagent tool and the user has not opted out; treat cross-module architecture, boot flow, data flow, integration wiring, security/privacy/money/data/API, or many-file mapping questions as large by default. Otherwise run `single-agent multi-lens` and say why no subagents were used when workflow trace is requested.

## Workflow

1. Restate the question and scope.
2. Restate authority boundaries and declare the ECF run mode when the user asks for
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有