eval-collector

Collects SDD workflow code changes and builds JSON evalset files from git diffs and tasks.md metadata.

52|3|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/ZTE-AICloud/Co-OmniSpec --skill eval-collector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eval-collector
Source: https://github.com/ZTE-AICloud/Co-OmniSpec/tree/main/skills/eval-collector
Command: npx skills add https://github.com/ZTE-AICloud/Co-OmniSpec --skill eval-collector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

本技能在 SDD 流程结束后,自动采集代码变更信息并生成评测所需的 JSON 文件,帮助评测系统快速获得任务变更数据。

Core Features & Use Cases

  • 从 changes/<branch>/tasks.md 提取 "目的" 行作为 feature_infos
  • 从 git diff 输出中提取实际变更片段作为 code_blocks
  • 将输出保存到 changes/<branch>/evalset/config.result.json

Quick Start

Execute the collect.py script to generate changes/<branch>/evalset/config.result.json for the current repository.

Frequently Asked Questions about eval-collector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate eval JSON from git diffs after an SDD workflow?

To generate eval JSON from git diffs after an SDD workflow, you execute the collect.py script. This script analyzes directory changes, extracts feature_infos from tasks.md, and builds code_blocks from git diffs to produce an evaluation-ready JSON artifact.

What is the structure of the evaluation-ready JSON payload produced from code changes?

The evaluation-ready JSON payload follows an api and input structure suitable for downstream automated evaluation. It is saved as config.result.json under the changes/<branch>/evalset directory, containing extracted feature_infos and code_blocks.

How does the tool extract feature_infos from tasks.md for automated evaluation?

The tool extracts feature_infos from tasks.md by locating and parsing lines labeled with the purpose description. These extracted lines are then included in the generated JSON payload to provide context for the code changes.

Do I need any specific dependencies to collect code change information for eval JSON?

You do not need specific external dependencies to collect code change information for eval JSON. The skill operates using internal scripts and relies on standard git diff outputs and the presence of a tasks.md file in the target directory.

Where is the generated evaluation JSON saved when collecting SDD code changes?

The generated evaluation JSON is saved directly to the changes/<branch>/evalset/config.result.json path. This ensures the evaluation payload is organized by branch and ready for automated evaluation systems to access.