Summarize testdata changes

Name: Summarize testdata changes
Availability: InStock
Author: carbon-language

Parse git diffs to categorize Carbon testdata edits into input, STDERR, and STDOUT.

33.9k|1.7k|Updated Apr 27, 2020

Search Tags:#git #diff #code-review #report #summarize #testdata

Ready to run

npx skills add https://github.com/carbon-language/carbon-lang --skill summarize-testdata-changes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Summarize testdata changes
Source: https://github.com/carbon-language/carbon-lang/tree/main/.agents/skills/summarize_testdata_changes
Command: npx skills add https://github.com/carbon-language/carbon-lang --skill summarize-testdata-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill provides a structured approach to summarizing changes made to Carbon's testdata files (toolchain/*/testdata) and correlating them with related code changes to improve traceability and review efficiency.

Core Features & Use Cases

Groups testdata changes by theme to reveal patterns across commits.
Captures both inputs and diagnostic outputs (STDERR/STDOUT) with file-level references for traceability.
Supports generating a report suitable for PRs, audits, and release notes.

Quick Start

Run the summarize_testdata_changes script to generate a grouped report of testdata changes.

Frequently Asked Questions about Summarize testdata changes

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

FAQPage Schema

How do I summarize testdata changes from a git diff for a code review?▼

This skill parses git diff outputs to categorize testdata changes into input, STDERR, and STDOUT, mapping them to related code changes and grouping them by theme for a structured code review report.

What is the best way to group testdata edits by theme during a release audit?▼

The best way to group testdata edits by theme is parsing git diff outputs to categorize changes into input, STDERR, and STDOUT, producing a structured report with file-level references for traceability.

Can I generate a structured report linking Carbon toolchain testdata updates to code changes?▼

Yes, you can generate a structured report linking Carbon toolchain testdata updates to code changes by running the summarize script to group edits by theme and detail file-level diagnostic outputs.

Does this approach capture diagnostic outputs like STDERR and STDOUT from testdata files?▼

Yes, this approach captures diagnostic outputs like STDERR and STDOUT from testdata files by parsing git diff outputs and categorizing edits into input, STDERR, and STDOUT with file-level references.

When do I need to map testdata edits to related code changes?▼

You need to map testdata edits to related code changes during code reviews and release audits where testdata changes occur, ensuring traceability and revealing patterns across commits through grouped themes.