agentleFS
DataWithBaraaDataWithBaraa/claude-code-data-engineering-skills/skills/test-data/SKILL.md

test-data

Skill84 starsChanged 13 days agoMITView on GitHub

Use when a new function or a new table needs tests, to write test data with the edge cases and the expected result written first, never from production data.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the tests and report which passed.

    line 21
  2. Distinctive:

    Never reads production data for a test.

    line 37
  3. Distinctive:

    Never writes under the data folders.

    line 38

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Test data

The job: small test files with the edge cases, and the expected result decided first.

Input: the function or the table under test.

Steps

  1. Name the function or the table under test, and what it must do with each edge case.
  2. Synthetic rows from the metadata, in the source's own format. Never real data.
  3. The expected result first: what the output must hold, written before the code.
  4. Injected faults, each with its expected result: a broken line, a new column, broken bytes, a child row before its parent.
  5. A second delivery with drift: a renamed column that the schema check must stop.
  6. The fixtures beside the tests, never in the data folders.
  7. Run the tests and report which passed.

Output

The test files beside the tests: the input rows, the injected faults, the expected result written first, and the test that compares them.

Reads

  • the metadata of the table, the file parsers of the source's format

Writes

  • the fixtures of the test, and the test

Never

  • Never reads production data for a test.
  • Never writes under the data folders.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.