generator-cleanup-audit

Identify and sequence behavior-preserving cleanups in Refitter's generator layer.

413|64|Updated Feb 7, 2023

Search Tags:#testing #cleanup #regression #code-quality #generator #refitter

Ready to run

npx skills add https://github.com/christianhelle/refitter --skill generator-cleanup-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: generator-cleanup-audit
Source: https://github.com/christianhelle/refitter/tree/main/.squad/skills/generator-cleanup-audit
Command: npx skills add https://github.com/christianhelle/refitter --skill generator-cleanup-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify and sequence behavior-preserving cleanups in Refitter's generator layer, reducing risk of regressions during large refactoring.

Core Features & Use Cases

Identify candidate cleanup opportunities in generator code without altering emitted output.
Provide sequencing guidelines to preserve public-output coverage and avoid breaking changes during regeneration.
Use cases include audits after AI-assisted changes to components like RefitInterfaceGenerator and related emitters to ensure stability.

Quick Start

Audit a generator change set for safe, behavior-preserving cleanups and verify emitted output remains unchanged.

Frequently Asked Questions about generator-cleanup-audit

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

FAQPage Schema

How do I safely clean up generator code without changing the emitted output?▼

To safely clean up generator code, identify behavior-preserving refactoring opportunities and sequence them to preserve public-output coverage. This approach ensures the emitted output remains unchanged during large AI-assisted change sets in the generator layer.

What is a behavior-preserving cleanup in a code generator?▼

A behavior-preserving cleanup is a refactoring action that improves code quality without altering the generator's emitted output. It requires documented cleanup patterns and test coverage to verify that regeneration yields identical public outputs.

How do I audit generator code after large AI-assisted changes?▼

Audit generator code after AI-assisted changes by reviewing emission paths for safe cleanup opportunities. Use this auditing process to sequence refactoring steps, verify test coverage, and prevent regressions in components like RefitInterfaceGenerator.

When should I sequence generator cleanups to avoid regression risk?▼

Sequence generator cleanups during large AI-assisted change sets in the generator layer. Proper sequencing with safeguards against ordering or dependency changes prevents regression risk and maintains public-output stability.

Does refactoring generator emission paths require test coverage for public output?▼

Yes, refactoring generator emission paths requires test coverage for public output to verify the emitted output remains unchanged. This test coverage acts as a safeguard against breaking changes during regeneration.

What are the limitations of behavior-preserving cleanups in generator code?▼

Limitations include the requirement for documented cleanup patterns and existing test coverage. Without these safeguards, cleanups risk altering ordering or dependencies, potentially changing the emitted output and causing regressions.