agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/garnet/.github/skills/configure-garnet-option/SKILL.md

configure-garnet-option

Skill12k starsChanged 10 days agoMITView on GitHub

Add or modify a Garnet server configuration option across startup parsing, defaults, programmatic options, runtime CONFIG, consumers, tests and documentation.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 2 mentionsSep 2026: 10 mentionsOct 2026: 21 mentionsNov 2026: 9 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the microsoft/garnet repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about microsoft/garnet

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

See all 74

Talked about on GitHub, Bluesky, YouTube, Hacker News, Stack Overflow and the web (74 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 11

6 more on Bluesky

On YouTube · 8

3 more on YouTube

On Hacker News · 2

On the web · 1

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Add or update libs/host/Configuration/Options.cs, its validation attribute in OptionsValidators.cs, libs/host/defaults.conf, the …

    line 11
  2. Distinctive:

    Keep help text, defaults comments and XML documentation consistent about units, defaults, bounds, scope and when changes take effect.

    line 14
  3. Very specific:

    Do not mutate startup options to implement CONFIG SET.

    line 20
  4. Distinctive:

    Use an update action when a live task or physical consumer must be changed.

    line 21
  5. Distinctive:

    Follow the existing net10.0 test-project layout.

    line 29
  6. Very specific:

    Update website/docs/getting-started/configuration.md and the feature's operator and developer documentation.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

Configure a Garnet option

Trace a comparable option before editing. Decide whether the value is startup-only, read live, captured per operation, or requires a lifecycle action.

  1. Add or update libs/host/Configuration/Options.cs, its validation attribute in OptionsValidators.cs, libs/host/defaults.conf, the corresponding GarnetServerOptions member and the Options.GetServerOptions() mapping.
  2. Keep help text, defaults comments and XML documentation consistent about units, defaults, bounds, scope and when changes take effect. Share parsers and validators.
  3. For runtime support, register a member in libs/server/Config/ServerConfigType.cs and metadata in libs/server/Config/RuntimeServerConfig.cs (RuntimeServerConfig.BuildMeta), seed it in Init, and use the declared typed accessor at every consumer. Register startup-only values as read-only when needed. Do not mutate startup options to implement CONFIG SET.
  4. Use an update action when a live task or physical consumer must be changed. Validate coupled settings before publication and capture a consistent snapshot for operations that cannot safely change halfway through. Check buffer pools, caches and resource sizing as well as the immediate consumer.
  5. Validate physical constraints with the configured provider without creating resources merely to probe them; retain defensive checks at the point of use.
  6. Cover CLI, JSON, defaults, programmatic validation, CONFIG GET/SET and GET *, rejection without mutation, actual consumer behavior and operation lifetime. Follow the existing net10.0 test-project layout.
  7. Update website/docs/getting-started/configuration.md and the feature's operator and developer documentation. Explain normalization and runtime update ordering.

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