agentleFS
Sign inStart free
faizkhairifaizkhairi/claude-code-blueprint/skills/db-check/SKILL.md

db-check

Skill73 starsChanged 4 months agoMITView on GitHub

Validate database schema integrity and check for common issues

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the ORM schema file (e.g., prisma/schema.prisma, drizzle/schema.ts, SQLAlchemy models, ActiveRecord schema, Entity Framework …

    line 9
  2. Distinctive:

    CRITICAL: Check all database tables have ORM models (unmodeled tables may be dropped on schema sync, e.g.

    line 10
  3. Distinctive:

    Check for missing indexes on foreign keys and frequently queried columns

    line 11
  4. Very specific:

    Verify undefined vs null usage in all ORM create/update operations

    line 13
  5. Distinctive:

    Check raw SQL queries for injection vulnerabilities (parameterized queries required)

    line 14
  6. Distinctive:

    Verify referential integrity (cascade rules, orphan prevention)

    line 15
  7. Distinctive:

    Check for date handling issues (check CLAUDE.md for system-specific date formats)

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Database health check for the current project:

  1. Read the ORM schema file (e.g., prisma/schema.prisma, drizzle/schema.ts, SQLAlchemy models, ActiveRecord schema, Entity Framework DbContext, GORM structs, or equivalent) and analyze all models
  2. CRITICAL: Check all database tables have ORM models (unmodeled tables may be dropped on schema sync, e.g. Prisma db push; know whether your ORM's sync command is destructive)
  3. Check for missing indexes on foreign keys and frequently queried columns
  4. Scan services for N+1 query patterns (missing eager loading / includes in queries)
  5. Verify undefined vs null usage in all ORM create/update operations
  6. Check raw SQL queries for injection vulnerabilities (parameterized queries required)
  7. Verify referential integrity (cascade rules, orphan prevention)
  8. Check for date handling issues (check CLAUDE.md for system-specific date formats)
  9. Review migration history for risky operations

Report findings with severity: CRITICAL / HIGH / MEDIUM / LOW.

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.

Check your setup, free