Skip to content
Back to skills

Schema Rules

ASecurity

Naming and structure rules for orchard database migrations.

  • 47 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 9, 2026
developmentdatabase

Security analysis

A100/100

Scanned November 9, 2026

npx -y skills add acoz-labs/quickstop --skill schema-rules --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Schema Rules?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Schema Rules
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/acoz-labs-schema-rules/badge)](https://www.skillsdirectory.com/skills/acoz-labs-schema-rules)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: schema-rules
description: Naming and structure rules for orchard database migrations.
---
# Schema rules

- One table per migration.
- Name a migration `<number>_<verb>_<table>`, for example `0042_add_reason_code_to_movements`.
- Every migration has a reverse step that restores the previous schema exactly.
- Quantities are `INTEGER`; never use `REAL` or `NUMERIC` for a count.
- Hand edits to anything in `migrations/` are not allowed; always generate a fresh migration through `bin/migrate new`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in development →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.