Skip to content
Skills Library
Programming · Automation

generated-artifact

/generated-artifact

Use when a committed file is produced by a generator that can be re-run.

Repository
Drift ↗
Licence
MIT
Last repository change
07.11.2026

Assessment and security

91/ 100Class: good
Format20 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability21 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 07.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when a committed file is produced by a generator that can be re-run.

Original author description

Use when a committed file is produced by a generator that can be re-run.

How it works

  1. The invariant
  2. The failure it prevents
  3. The probe
  4. The repair
  5. Pitfalls
  6. Claim-to-test
Original SKILL.md headings · 85 lines, 597 words
SKILL.md preview
---
name: generated-artifact
description: "Use when a committed file is produced by a generator that can be re-run."
version: 1.0.0
author: Hermes Agent
license: MIT
platforms: [macos, linux]
category: Derive
metadata:
  hermes:
    tags: [generated, schema, drift, artifact, producer]
    related_skills: [mirror-copy]
---

# Generated Artifact

A committed artifact is the output of a program, and the program keeps changing.
The file and the program are two statements of one truth.

## The invariant

**Every committed artifact equals what its producer writes today.**

## The failure it prevents

A model gains a field; the schema file does not. Nothing fails, because the file
is valid - it is simply older than the code that reads it. The consumer of the
schema then rejects a field the writer sends, or accepts one that no longer
exists, and the error surfaces at the boundary rather than at the commit that
caused it.

The same failure with a different symptom: an artifact regenerated by hand with a
different tool version, so a formatting change and a content change arrive in one
diff and nobody can separate them.

## The probe

The only honest test is to run the producer and look at what changed. Timestamps
prove nothing; a file can be newer than its producer and still wrong.

Capture the artifact, run the producer, compare, then put it back:

```sh
shasum -a 256 <artifact> > /tmp/before
<producer> --write
shasum -a 256 <artifact> | diff /tmp/before -
```

A non-empty diff is drift. Restore the committed bytes afterwards unless the run
was meant to regenerate them.

Most generators carry the comparison themselves, which is better than wrapping
one: a compare mode that exits non-zero on drift, and a flag that regenerates.

Prefer that form. A producer with a regenerate flag and a compare-by-default mode
is a guard; a producer that only writes is a build step that happens to overwrite
a tracked file.

## The repair

Regenerate, then read the diff before committing it. A regenerated artifact whose
diff contains only the change you made is the expected outcome; one whose diff
contains reordered keys or reformatted output is a producer change that arrived
unnoticed, and it belongs in its own commit.

```sh
<producer> --write
git diff --stat -- <artifacts>
```

## Pitfalls

- **A producer that rewrites unconditionally makes every check a drift report.**
  If it cannot compare, wrap it: snapshot, run, compare, restore.
- **A producer run in the wrong directory writes to the wrong place, or fails
  silently.** State the working directory; a script that resolves paths relative
  to its own file is not the same as one that resolves them relative to the
  caller.
- **A build-directory copy is not a committed artifact.** Regenerating into a
  gitignored output directory proves the producer runs, not that the committed
  file is current. Check the tracked path.
- **A generator that imports through a bundler alias fails when run by bare
  Node.** The alias resolves in the page build and not in the script, which makes
  the guard report drift that is really a resolution failure. Import by the real
  path.
- **A producer that exits 0 while writing nothing looks like agreement.** Compare
  the artifact's digest before and after, not the exit code. A missing artifact
  after a successful run is drift.

## Claim-to-test

| Claim | Probe | Pass condition |
| --- | --- | --- |
| The artifact is current | the producer in compare mode | exit 0 |
| The producer actually writes it | run with `--write`, then `ls -l <artifact>` | mtime advanced, digest matches a second run |
| Regeneration is stable | run `--write` twice, digest after each | identical digests |
| Only intended content changed | `git diff -- <artifacts>` | the diff is the change that was made |

Versions

The database has no other skills named generated-artifact.

Database snapshot: 13.11.2026 · package version f2aee54d70a9 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100api-test-generator
    Generate api test generator operations. Auto-activating skill for Test Automation. Triggers on: api test generator, api test generator Part of the Test Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like "api test generator",…
  • 100api-client-generator
    Generate api client generator operations. Auto-activating skill for API Integration. Triggers on: api client generator, api client generator Part of the API Integration skill category. Use when working with APIs or building integrations. Trigger with phrases like "api client…
  • 84using-generated-regex
    Implements compile-time regex using GeneratedRegexAttribute Source Generator. Use when working with Regex patterns for better performance and AOT compatibility.
  • 100conformetry-generate
    Scaffold code with a conformetry generator instead of writing it by hand. Use when adding a module, component, service, application, or package to a workspace that has a conformetry configuration; when deciding whether a generator exists for the shape you are about to create;…
  • 100conformetry-generate
    Scaffold code with a conformetry generator instead of writing it by hand. Use when adding a module, component, service, application, or package to a workspace that has a conformetry configuration; when deciding whether a generator exists for the shape you are about to create;…
  • 100including-generated-files
    Own MSBuild generated-artifact integration. USE FOR: a target that creates or should create source, Content, None, or another physical file but the artifact is missing from compilation or output; target timing; evaluation-time glob misses; $(IntermediateOutputPath) placement;…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.