agentleFS
Sign inStart free
AWSKnown publisheraws/karpenter-provider-aws/website/content/en/preview/upgrading/AGENTS.md

karpenter-provider-aws / upgrading

AGENTS.md7.7k starsChanged 36 days agoApache-2.0View on GitHub

These rules apply when you add or edit the per-version notes in upgrade-guide.md (the ### Upgrading to <version>+ sections). Rank notes within each group by impact as well. For metrics, that means how much observability breaks, e.g. how widely the metric is used and how many queries the change breaks. - This file isn't published: website/hugo.yaml lists AGENTS.md in ignoreFiles.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 1 mentionMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 2 mentionsJul 2026: 4 mentionsAug 2026: 0 mentionsSep 2026: 7 mentionsOct 2026: 6 mentionsNov 2026: 2 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the aws/karpenter-provider-aws repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about aws/karpenter-provider-aws

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

See all 40

Talked about on GitHub and Bluesky (40 times).

On GitHub · 38

33 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,542 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:

    Every breaking change needs an upgrade guide note, and the note starts with Breaking:.

    line 5

≈ “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

Upgrade guide notes

These rules apply when you add or edit the per-version notes in upgrade-guide.md (the ### Upgrading to <version>+ sections).

  • Every breaking change needs an upgrade guide note, and the note starts with **Breaking:**.

  • Order each version's notes by priority, which is how big the impact is on users who upgrade:

    1. Breaking changes, which affect everyone who upgrades. Keep them together at the top: behavior changes first, then metrics changes (whose impact is broken observability, e.g. dashboards and alerts). Put a change's escape hatch or migration note right after it.
    2. Notes that aren't breaking but still need action from some users, e.g. a changed default.
    3. Deprecations, which only matter if you use the deprecated feature.
    4. New opt-in feature gates, which only matter if you turn them on.

    Rank notes within each group by impact as well. For metrics, that means how much observability breaks, e.g. how widely the metric is used and how many queries the change breaks.

  • This file isn't published: website/hugo.yaml lists AGENTS.md in ignoreFiles.

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