agentleFS
MicrosoftKnown publishermicrosoft/bobsql/.github/skills/inside-transaction-log/SKILL.md

inside-transaction-log

Skill1 starsChanged 12 days agoMITView on GitHub

Explore SQL Server transaction log files, VLFs, log records, log IO, minimal logging, recovery, truncation, and log management. Use when working with examples/insidetlog or selecting its five transaction-log labs and VLF tests.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the collection map. Choose physical layout, records, IO, recovery, management, or VLF growth.

    line 10
  2. Distinctive:

    Read the selected walkthrough and scripts before deciding execution order.

    line 12
  3. Distinctive:

    Treat internal DBCC/log-format details as version-sensitive educational evidence.

    line 21
  4. Distinctive:

    Use secret checks before publishing scripts, backups, or log captures.

    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

Inside the transaction log

Procedure

  1. Read the collection map. Choose physical layout, records, IO, recovery, management, or VLF growth.
  2. Read the selected walkthrough and scripts before deciding execution order. Confirm SQL build, SQL tools, permissions, filesystem/backup paths, and any extra inspection utilities.
  3. Require an isolated lab and explicit approval for shutdown, restore, file manipulation, log rebuilding, large growth, or destructive cleanup. Preserve restorable lab backups before recovery experiments.
  4. Establish the documented starting database state. Run the selected blocks and separate sessions in order, recording actual VLF, log-space, record, IO, transaction, or recovery observations at the requested checkpoints.
  5. Treat internal DBCC/log-format details as version-sensitive educational evidence. Do not turn a lab's file/log-rebuild technique into production recovery advice or infer results from historical screenshots.
  6. Close transactions, stop drivers, restore the intended lab state, and report remaining files/databases rather than deleting them automatically.

Use secret checks before publishing scripts, backups, or log captures; binary artifacts need independent review.

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.