agentleFS
Sign inStart free
CloudflareKnown publishercloudflare/cf/packages/wrangler-tests/AGENTS.md

cf / wrangler-tests

AGENTS.md1k starsChanged 9 days agoApache-2.0View on GitHub

This package runs canonical Wrangler test situations against cf. The pinned revision, inventory shape, and regeneration command are documented in README.md; MANIFEST.md is the generated inventory. - Upstream test names and describe() ancestry are canonical identities. Do not rename or delete them when adapting command paths or assertions for cf. - A passing test is executable parity evidence. Use it.todo() when the behavior belongs in cf but is not working or ported yet. Use it.skip() only for Wrangler internals or…

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about cloudflare/cf

The biggest 5 of 25 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 25

Talked about on GitHub and Bluesky (25 times).

On GitHub · 24

19 more on GitHub
  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository2 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run pnpm test from this package.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “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
AGENTS.md

Wrangler compatibility tests

This package runs canonical Wrangler test situations against cf. The pinned revision, inventory shape, and regeneration command are documented in README.md; MANIFEST.md is the generated inventory.

Canonical identities

  • Upstream test names and describe() ancestry are canonical identities. Do not rename or delete them when adapting command paths or assertions for cf.
  • A passing test is executable parity evidence. Use it.todo() when the behavior belongs in cf but is not working or ported yet. Use it.skip() only for Wrangler internals or behavior that deliberately conflicts with cf's design.
  • Missing upstream identities default to todo. Broad skip rules require explicit review; do not turn unaudited behavior into an intentional divergence.
  • Normal ported tests take precedence over generated fallback classifications.

Generated inventory

  • src/__tests__/upstream/unported-*.test.ts and MANIFEST.md are generated by scripts/generate-upstream-stubs.mjs. Do not edit individual manifest rows or fallback identities by hand.
  • The generator requires complete Vitest JSON reports, not vitest list output. It uses full ancestry when leaf titles repeat and preserves expanded parameterized cases.
  • Rebase the corpus atomically: update the pinned revision/banner, classification rules, every fallback shard, and the full manifest in one reviewable change.

Verification

Run pnpm test from this package. Its Vite+ task depends on CLI generation and the test-specific Vite+ Pack build, and tests import the resulting ../cli/dist/index.mjs. The test build keeps mock-sensitive dependencies external while the normal production build bundles them. pnpm test:watch has the same prerequisites, run once before starting Vitest. Task caching is disabled.

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.

Check your setup, free