Curated library of atomic AI agent skills for Hanami, dry-rb, and ROM Ruby development. Covers actions, slices, repositories, relations, changesets, providers, DI, operations, TDD, CLI, views, routing, and validation. Shared Ruby process skills have moved to ruby-core-skills. Uses Markdown + Front-matter architecture.
92
94%
Does it follow best practices?
Impact
92%
1.33xAverage score across 35 eval scenarios
Passed
No known issues
Use this skill when running Hanami 2.x database CLI commands.
Core principle: Database commands are environment-aware. Always confirm HANAMI_ENV and DATABASE_URL before running destructive commands.
| Command | Purpose | Preconditions | Validate |
|---|---|---|---|
hanami db create | Create the database | DATABASE_URL must be set | - |
hanami db drop | Drop the database | Warning: Destructive - see below | - |
hanami db migrate | Run pending migrations | Database must exist | hanami db version |
hanami db rollback | Roll back the last migration | Database must exist; migration must be reversible | hanami db version |
hanami db seed | Run seed data | Database must exist; migrations must be current | - |
hanami db prepare | Create + migrate + seed (development) | DATABASE_URL must be set | - |
hanami db version | Show current migration version | Database must exist | - |
Create the database:
DATABASE_URL=postgres://localhost/my_app_development hanami db createRun migrations (validate with hanami db version - prints timestamp of last applied migration):
hanami db migrate
hanami db versionRoll back the last migration (only works if migration is reversible - change block, or explicit up/down; drop_column/rename_column require explicit up/down):
hanami db rollback
hanami db version # Should print the previous migration's timestampRun seed data (db/seeds.rb is executed):
hanami db seed# db/seeds.rb
# frozen_string_literal: true
rom = Hanami.app["db.rom"]
users = rom.relations[:users]
users.insert(email: "admin@example.com", first_name: "Admin", role: "admin")Prepare the database:
hanami db prepare
hanami db dropdeletes all data and cannot be undone. Always validate before proceeding.
Safe drop procedure:
echo $HANAMI_ENV # Must output "development" or "test" - never "production"
hanami db drop # Only proceed if environment is confirmedPreconditions for all commands:
DATABASE_URL environment variable is setdb create / db drop)| Mistake | Reality |
|---|---|
| "I'll edit a migration file after it has been run" | Do not edit ran migrations. Create a new migration to fix the schema. |
"I'll skip hanami db seed because I don't have seed data yet" | Create an empty db/seeds.rb so hanami db prepare works. Add seed data later. |
"I'll run hanami db rollback on an irreversible migration" | drop_column and rename_column migrations require explicit up/down. Rolling back a change-only irreversible migration fails. |
| Related Skill | When to chain |
|---|---|
| write-migration | Create migration files before running hanami db migrate. |
| create-app | Database commands are used after creating the app. |
| define-relation | Verify Relations match the migrated schema. |
| write-request-spec | Test database setup may need hanami db prepare. |
docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31
scenario-32
scenario-33
scenario-34
scenario-35
skills
actions
build-json-api
create-action
handle-errors
validate-params
context
load-context
db
create-changeset
create-repository
define-relation
write-migration
dry-monads
handle-result-pattern
dry-rb
create-operation
create-validation-contract
providers
configure-providers
implement-di
review-security
routing
define-routes
slices
configure-slice
create-slice
extract-slice
review-slice-boundaries
test-slice