agentleFS
MicrosoftKnown publishermicrosoft/bobsql/.github/skills/waits-latches-spinlocks/SKILL.md

waits-latches-spinlocks

Skill1 starsChanged 12 days agoMITView on GitHub

Investigate SQL Server waits, scheduler yield, buffer latches, LOCK_HASH spinlocks, and Azure SQL log governance. Use when working with examples/insidewaitslatchesspinlocks and its debugwaits, latches, spinlocks, or loggovernance areas.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    Use the collection map to choose the scenario.

    line 10
  2. Distinctive:

    Use a disposable lab. Obtain approval before restarts, debugger attachment, Resource Governor changes, heavy traffic, bulk inserts, or …

    line 16
  3. Distinctive:

    Run the approved workload in the intended sessions, then compare deltas and stacks rather than equating a cumulative wait count with the …

    line 20
  4. Distinctive:

    Stop the specific lab processes, close transactions, detach the debugger, and follow the chosen cleanup while restoring prior settings.

    line 24
  5. Distinctive:

    Do not run contention or failure reproductions in production.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Waits, latches, and spinlocks

Procedure

  1. Use the collection map to choose the scenario. Read its Markdown entry point and retained readme.txt instructions.
  2. Confirm platform, SQL build/tier, instance, SQL tools, and the scenario's WinDbg/symbol or stress-driver dependencies. Review startup flags, authentication, local paths, and resource limits.
  3. Use a disposable lab. Obtain approval before restarts, debugger attachment, Resource Governor changes, heavy traffic, bulk inserts, or configuration changes. Supply credentials privately; do not reuse literal demo passwords.
  4. Capture baseline requests, wait/latch/spinlock counters, and CPU/log metrics. Run the approved workload in the intended sessions, then compare deltas and stacks rather than equating a cumulative wait count with the root cause.
  5. Resolve spinlock type IDs and internal symbols against the current build. Captured driver output is reference material, not proof of current behavior.
  6. Stop the specific lab processes, close transactions, detach the debugger, and follow the chosen cleanup while restoring prior settings.

Do not run contention or failure reproductions in production. Follow secret checks before publishing logs or scripts.

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.