agentleFS
Sign inStart free
LeostrukaLeostruka/devin-bundle/skills/database/SKILL.md

database

Skill0 starsChanged 3 months agoMITView on GitHub

Use when the user wants to design, migrate, query, or optimize a database. Covers schema design, migrations, query review, indexing, and data integrity.

31 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use monitoring, ci-cd and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • rogue-dev-studioSkill

    monitoring

    Claude monitoring and usage tracking tools (UV, claude-monitor, claude-usage-cli). Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `monitoring` work when listed in TEAM.yaml or explicitly requested.

    Also in 3 projects that use this

  • JohnJBorenSkill

    ci-cd

    CI/CD pipeline design, GitHub Actions, testing automation, and deployment strategies

    Also in 4 projects that use this

  • JkudjoSkill

    incident

    Production incident response — structured triage, hypothesis tree, safe remediation, incident record

    Also in 3 projects that use this

  • mrgoonieSkill

    devops

    Deploy to Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Kubernetes (kubectl, Helm). Use for serverless, containers, CI/CD, GitOps, security audit.

    Also in 4 projects that use this

  • GitHubSkill

    state-management

    CoreAI Sandbox's TanStack Query + mock-JSON data layer. USE WHEN: editing data-fetching hooks (`app/hooks/use*.ts`), adding mock data in `app/data/`, or wiring a component to query state.

    Also in 3 projects that use this

  • OpenAISkill

    observability

    Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 7

    Distinctive

    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:

    Understand the model: Read existing schema, migrations, and ORM config.

    line 20
  2. Distinctive:

    Design or change schema: Use migrations; never edit schema directly in production.

    line 21
  3. Distinctive:

    Review queries: Check indexes, N+1, transactions, and locks.

    line 22
  4. Distinctive:

    Run migrations locally: Verify roll-forward and roll-back.

    line 23
  5. Distinctive:

    Document: Update migration log and schema docs.

    line 25
  6. Distinctive:

    After schema changes, run migration tests and a sample query plan.

    line 34
  7. Distinctive:

    Commit migration files and update CHANGELOG.

    line 35

“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “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

Database

Database design, migrations, and query optimization.

When to use

  • New schema or migration is needed.
  • Query is slow or returns wrong results.
  • Data integrity or constraints must be added.
  • Backup/restore or seeding is required.

Core protocol

  1. Understand the model. Read existing schema, migrations, and ORM config.
  2. Design or change schema. Use migrations; never edit schema directly in production.
  3. Review queries. Check indexes, N+1, transactions, and locks.
  4. Run migrations locally. Verify roll-forward and roll-back.
  5. Validate data. Seed, constraints, and referential integrity.
  6. Document. Update migration log and schema docs.

See also

  • data-analyst — SQL-first data exploration and charts.
  • database — schema design, migrations, and query optimization.

Output rule

  • After schema changes, run migration tests and a sample query plan.
  • Commit migration files and update CHANGELOG.

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.

Reviews can't be read right now.

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