sqlite-adonet
Implementation details for the Microsoft.Data.Sqlite ADO.NET provider. Use when changing files under src/Microsoft.Data.Sqlite.Core/.
- Installs
- 48
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/dotnet/efcore --skill sqlite-adonet- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads sqlite-adonet automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Microsoft.Data.Sqlite
Standalone ADO.NET provider in src/Microsoft.Data.Sqlite.Core/, independent of EF Core. Implements System.Data.Common abstractions.
Notable Implementation Details
- Static constructor calls
SQLitePCL.Batteries_V2.Init()reflectively CreateFunction()/CreateAggregate()overloads generated from T4 templates (.ttfiles)
Command Lifecycle
SqliteConnection tracks associated commands as weak references. Closing an open connection disposes every live tracked command before closing the native connection; command disposal releases prepared statements and unregisters the command. Diagnose close/reopen reports from this ownership path and the System.Data.Common contract, not from EF Core provider abstractions.
Closing does not erase the command's managed configuration or connection reference. If the same command object is used after reopening its connection, execution prepares fresh native statements against the new handle. Add a regression test only when the reported behavior remains reachable after following this lifecycle.
Transaction Completion
A failed COMMIT can leave the SQLite transaction active and retryable. Do not call Complete() or add transaction-level retries; SqliteCommand already retries busy/locked results through the connection's ExecuteNonQuery path.
Rollback during disposal must detach the managed transaction even when rollback throws, so keep Complete() in its finally. Test failed commit separately from failed Dispose()/DisposeAsync(): preserve the original exception and verify disposal permits a subsequent transaction.
FAQ
What does the sqlite-adonet skill do?
Implementation details for the Microsoft.Data.Sqlite ADO.NET provider. Use when changing files under src/Microsoft.Data.Sqlite.Core/.
How do I install sqlite-adonet?
Run npx skills add https://github.com/dotnet/efcore --skill sqlite-adonet in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/sqlite-adonet/ (personal) or .claude/skills/sqlite-adonet/ (project).
Which AI agents can use sqlite-adonet?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is sqlite-adonet safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains sqlite-adonet?
It is published by dotnet in dotnet/efcore. It has 48 recorded installs.
More from dotnet/efcore
model-building
dotnet/efcore
Open the skill to read its SKILL.md instructions.
tooling
dotnet/efcore
Implementation details for the EF Core dotnet-ef CLI and tooling. Use when changing dotnet-ef commands, the ef wrapper, EFCore.Tools (PMC), or EFCore.Tasks MSBuild integration.
update-pipeline
dotnet/efcore
Open the skill to read its SKILL.md instructions.
change-tracking
dotnet/efcore
Open the skill to read its SKILL.md instructions.
query-pipeline
dotnet/efcore
Open the skill to read its SKILL.md instructions.
Popular data & databases skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pgcron, pgmq), vector/semantic search (pgvector), and restoring dumps (pgrestore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-client-api
prisma/skills
Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on "prisma query", "findMany", "create", "update", "delete", "$transaction".
prisma-database-setup
prisma/skills
Deprecated compatibility name for prisma-orm-setup. Use only when a user or existing integration explicitly invokes prisma-database-setup; otherwise select prisma-orm-setup.
prisma-cli
prisma/skills
Prisma ORM 7 CLI reference for existing Prisma 7 applications or explicitly selected Prisma 7 workflows. Covers prisma init, generate, migrate, db, dev, studio, and mcp. For setup, connection repair, or Prisma 8, use prisma-orm-setup; not the Prisma Platform CLI.
prisma-postgres
prisma/skills
Deprecated compatibility name for prisma-postgres-setup. Use only when a user or existing integration explicitly invokes prisma-postgres; otherwise select prisma-postgres-setup.
prisma-driver-adapter-implementation
prisma/skills
Required reference for Prisma ORM 7 SQL driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter, Transaction, savepoint, result mapping, or DriverAdapterError behavior. Covers current transaction lifecycle, optional savepoint hooks, original database-error preservation, and verification.