smithery/ddobrin

database-analyst

Analyzes database schemas, migrations, ORM entities, and repository pattern across Java, Kotlin, and Python codebases. Identifies performance issues, N+1 queries, locking risks, normalization violations, and generates ERD documentation

Installation

$ npx skills add smithery/ddobrin --skill database-analyst

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/ddobrin.

npx skills add smithery/ddobrin

Browse all from smithery/ddobrin

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,467 B
  • docs SUMMARY.md 259 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Database Analyst

Usage

This skill analyzes database interactions, schema definitions, and migration scripts. It supports:

  • Languages: Java (Spring Data JPA, Hibernate), Kotlin (Exposed), Python (SQLAlchemy, Alembic)
  • Tasks: Performance analysis, Schema design review, Application logic audit, ERD generation.

Workflows

1. Identify Technology Stack

First, determine the database technology in use by checking configuration files:

  • Java/Spring: Look for pom.xml (dependencies like spring-boot-starter-data-jpa, flyway-core), application.properties, and Entity classes (@Entity).
  • Python: Look for requirements.txt (sqlalchemy, alembic), alembic.ini, and model definitions (Base = declarative_base()).

2. Select Analysis Mode

Based on the user's request, perform the following:

A. Performance & Migration Analysis

For requests about "slow queries", "locking", "migrations", or "tuning":

  1. Locate migration files (e.g., src/main/resources/db/migration/.sql or alembic/versions/.py).
  2. Review for locking risks and anti-patterns.
  3. Read [references/performance.md](references/performance.md) for specific checklists.

B. Schema Design & ERD

For requests about "normalization", "schema review", "database structure", or "diagrams":

  1. Locate Entity/Model classes.
  2. Analyze relationships, constraints, and keys.
  3. Read [references/schema.md](references/schema.md) for normalization rules and ERD formatting.

C. Application Logic & Query Analysis

For requests about "N+1 problems", "repository review", or "transaction issues":

  1. Locate Repository/DAO layers and Service layers.
  2. Trace method calls to identify implicit queries.
  3. Read [references/java-jpa.md](references/java-jpa.md) for Java/Spring specifics.
  4. Read [references/python-sqlalchemy.md](references/python-sqlalchemy.md) for Python specifics.

Output Format

  • Analysis: Group findings by "Critical", "Warning", and "Info".
  • ERD: Use Mermaid diagram format unless requested otherwise.
  • Recommendations: Provide concrete code snippets for fixes (e.g., adding an index, refactoring a query).