agentleFS
MicrosoftKnown publishermicrosoft/bobsql/.github/skills/sql-versioning/SKILL.md

sql-versioning

Skill1 starsChanged 12 days agoMITView on GitHub

Run the SQLBits 2026 SQL Server versioning demos: blocking, RCSI versus Snapshot, update conflicts, version chains, ADR/PVS cleanup, optimized locking, and benchmark comparisons. Use when working with examples/sqlversioning. For the local browser click-through apps, also load sql-versioning-apps.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Read the demo inventory. Work from examples/sqlversioning.

    line 15
  2. Very specific:

    Verify SQL Server 2025 and permissions.

    line 18
  3. Very specific:

    Run tools/check-readiness.ps1 with reviewed targets before the session.

    line 20
  4. Distinctive:

    Verify the intended evidence: blocking versus consistent reads, conflict errors, version-chain structure, PVS cleanup, or lock counts.

    line 27
  5. Distinctive:

    Follow secret checks; do not publish private connection details in viewer configuration or result files.

    line 37

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

SQL Server versioning explained

For browser-based demos 0-4, load the sql-versioning-apps skill. In this repository, "run the app" means verify/start the backend and open a new normal external browser window, not the VS Code integrated browser.

Procedure

  1. Read the demo inventory. Work from examples/sqlversioning; the descriptive demo folders retain their numeric prefixes. Use the inventory's current paths.
  2. Verify SQL Server 2025 and permissions. Inspect demo0-setup/demo0-setup.sql for database names/data creation and get approval before executing. Run tools/check-readiness.ps1 with reviewed targets before the session.
  3. Choose the desired concept and open session1/session2 scripts in separate SSMS windows. Follow their handoff cues; do not batch-run both sides or leave snapshot transactions open between demonstrations.
  4. For DBCC PAGE viewers, inspect the viewer source/configuration, confirm Python dependencies, and start only the required local viewer. Preserve autocommit behavior so diagnostic connections do not pin version cleanup.
  5. Verify the intended evidence: blocking versus consistent reads, conflict errors, version-chain structure, PVS cleanup, or lock counts. Internal page formats and cleanup timing are not stable production contracts.
  6. For throughput tests, read the benchmark guide, verify sqlsim, approve database creation/load, and preserve comparable configurations. Do not quote captured numbers as new measurements.
  7. Close all transactions, stop viewers/drivers by their specific process IDs, and confirm lab state before any requested cleanup.

Follow secret checks; do not publish private connection details in viewer configuration or result files.

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.