generated-file-manifest

Parse GeneratedFile markers to track files produced by build tooling.

413|64|Updated Feb 7, 2023

Search Tags:#automation #markers #build-tools #msbuild #generated-file #output-tracking

Ready to run

npx skills add https://github.com/christianhelle/refitter --skill generated-file-manifest

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use CLI-emitted generated-file markers to accurately reflect which files were created by a build or generation process, preventing drift between predictions and actual outputs.

Core Features & Use Cases

Emit a stable, machine-readable GeneratedFile marker (e.g., GeneratedFile: C:\path\to\File.cs) after a successful write to serve as the single source of truth.
Enable downstream tooling to parse these markers for compile items, manifests, or follow-up processing.
Fail loudly if a generator reports zero generated files to avoid silent, downstream issues.

Quick Start

Use the marker-based approach to track files produced by your code generator.

Frequently Asked Questions about generated-file-manifest

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

FAQPage Schema

How do I track generated files produced by MSBuild tasks for downstream processing?▼

To track generated files in MSBuild tasks, you can emit a stable, machine-readable GeneratedFile marker (e.g., GeneratedFile: C:\path\to\File.cs) after a successful write. Downstream tooling can then parse these markers to accurately reflect which files were created.

What is a generated file marker and how does it work for build automation?▼

A generated file marker is a stable, machine-readable string emitted after a successful file write during build automation. It serves as the single source of truth, enabling downstream tooling to parse exact outputs and prevent drift between predictions and actual files.

How can I prevent silent failures when my code generator reports zero output files?▼

To prevent silent failures when a code generator reports zero output files, configure your build tooling to fail loudly. This approach avoids silent, downstream issues by ensuring the process halts if no generated files are detected.

Does output tracking with machine-readable markers work with wrapper scripts and IDE extensions?▼

Yes, output tracking with machine-readable markers works with wrapper scripts and IDE extensions. You can apply this marker-based approach to any tooling that needs to track exact outputs across generation steps for deterministic downstream processing.

Why should I use generated file markers instead of predicting build outputs?▼

You should use generated file markers instead of predicting build outputs to prevent drift. Predicting outputs can cause mismatches, but parsing stable GeneratedFile markers after successful writes provides an accurate single source of truth for downstream tooling.