Loading...

Back to Details

erda-spec

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

ERDA Spec

ERDA 规范

This skill explains ERDA spec files from parser-supported structure first.

Current scope:

```
dice.yml
```
field index and structure
```
pipeline.yml
```
field index and structure
common action capability summaries
demo-derived best-practice pipeline composition patterns
parser-grounded guidance for reviewing or authoring these files

Current non-goals:

live marketplace lookup
action/addon search
runtime or pipeline execution guidance

This skill is backed by summarized references derived from ERDA source analysis:

source mapping:
```
references/source-map.md
```
dice fields:
```
references/diceyml-fields.md
```
pipeline fields:
```
references/pipelineyml-fields.md
```
semantic notes:
```
references/semantic-notes.md
```
action capabilities:
```
references/action-capabilities.md
```
best practices:
```
references/best-practices.md
```

dice.yml

review checklist:

references/diceyml-review-checklist.md

pipeline.yml

review checklist:

references/pipelineyml-review-checklist.md

本技能首先从解析器支持的结构出发，解释ERDA规范文件。

当前覆盖范围：

```
dice.yml
```
字段索引与结构
```
pipeline.yml
```
字段索引与结构
常见操作能力汇总
基于演示案例的最佳实践流水线组合模式
基于解析器的规范文件审查或编写指导

当前不包含的目标：

实时市场查询
操作/插件搜索
运行时或流水线执行指导

本技能基于ERDA源码分析得到的汇总参考资料：

源码映射：
```
references/source-map.md
```
dice字段：
```
references/diceyml-fields.md
```
pipeline字段：
```
references/pipelineyml-fields.md
```
语义说明：
```
references/semantic-notes.md
```
操作能力：
```
references/action-capabilities.md
```
最佳实践：
```
references/best-practices.md
```

dice.yml

审查清单：

references/diceyml-review-checklist.md

pipeline.yml

审查清单：

references/pipelineyml-review-checklist.md

Use This Skill For

使用本技能的场景

explaining what fields are supported in
```
dice.yml
```
explaining what fields are supported in
```
pipeline.yml
```
explaining what parser behavior or validation is implied by a field
explaining what a common pipeline action supports
mapping a project stack to a recommended action chain
reviewing a spec file against parser-supported structure
reviewing a
```
dice.yml
```
systematically
reviewing a
```
pipeline.yml
```
systematically
drafting a spec file with parser-compatible fields
answering "is this field supported?" questions

解释
```
dice.yml
```
中支持的字段
解释
```
pipeline.yml
```
中支持的字段
解释字段对应的解析器行为或验证规则
解释常见流水线操作支持的功能
将项目栈映射为推荐的操作链
根据解析器支持的结构审查规范文件
系统化审查
```
dice.yml
```
系统化审查
```
pipeline.yml
```
使用兼容解析器的字段起草规范文件
回答“该字段是否受支持？”之类的问题

Workflow

工作流程

Identify whether the request is about
```
dice.yml
```
,
```
pipeline.yml
```
, action capability, or a combination of them.
Decide whether the answer is primarily about:
- file structure and supported YAML fields
- action capability and expected params or outputs
- best-practice composition across multiple actions
Ground structure answers in the parser-derived field index, not in guesswork or market descriptions.
Ground action answers in the summarized action capability reference, not in generic CI/CD assumptions.
Use the semantic notes reference when a field exists but the real question is how merge, validation, upgrade, ref, or default dependency behavior works.
When a user asks about support, distinguish clearly between:
- field exists in the parser structure
- field may still require semantic validation elsewhere
If the request mixes file structure with action capability, answer the structure part first, then map the relevant actions and outputs.
Prefer concise field-level answers with exact YAML names.
When the user asks for a review, use the relevant review checklist instead of giving loose commentary.
When a user asks for a recommended pipeline, prefer the demo-derived patterns in the best-practices reference.
Do not expose development-machine paths or tell the user to inspect local source trees that are not part of the distributed skill.

判断请求是否涉及
```
dice.yml
```
、
```
pipeline.yml
```
、操作能力，或其中的组合。
判断答案主要涉及以下哪类内容：
- 文件结构与支持的YAML字段
- 操作能力及预期参数或输出
- 多操作组合的最佳实践
结构相关的答案需基于解析器生成的字段索引，而非猜测或市场描述。
操作相关的答案需基于汇总的操作能力参考资料，而非通用CI/CD假设。
当字段存在但用户实际询问的是合并、验证、升级、引用或默认依赖行为时，需参考语义说明资料。
当用户询问支持情况时，需明确区分：
- 字段是否存在于解析器结构中
- 字段是否可能需要其他地方的语义验证
如果请求同时涉及文件结构和操作能力，先回答结构部分，再映射相关操作及输出。
优先提供简洁的字段级答案，并使用准确的YAML名称。
当用户要求审查时，使用对应的审查清单，而非给出松散的评论。
当用户要求推荐流水线时，优先采用最佳实践参考资料中基于演示案例的模式。
不得暴露开发机器路径，也不得告知用户检查不属于分布式技能的本地源码树。

References

参考资料

Source map:
```
references/source-map.md
```
```
dice.yml
```
field index:
```
references/diceyml-fields.md
```

pipeline.yml

field index:

references/pipelineyml-fields.md

Semantic notes:
```
references/semantic-notes.md
```
Action capabilities:
```
references/action-capabilities.md
```
Best practices:
```
references/best-practices.md
```

dice.yml

review checklist:

references/diceyml-review-checklist.md

pipeline.yml

review checklist:

references/pipelineyml-review-checklist.md

源码映射：
```
references/source-map.md
```
```
dice.yml
```
字段索引：
```
references/diceyml-fields.md
```

pipeline.yml

字段索引：

references/pipelineyml-fields.md

语义说明：
```
references/semantic-notes.md
```
操作能力：
```
references/action-capabilities.md
```
最佳实践：
```
references/best-practices.md
```

dice.yml

审查清单：

references/diceyml-review-checklist.md

pipeline.yml

审查清单：

references/pipelineyml-review-checklist.md