Przejdź do treści
Biblioteka skilli
Programowanie · Przegląd i audyt

database-review

/database-review

Sprawdza bazy danych tylko do odczytu: PostgreSQL, MySQL, Redis, DynamoDB i RDS, pod kątem wolnych zapytań, indeksów i kosztów.

Repozytorium
RayStack ↗
Licencja
MIT
Ostatnia zmiana repozytorium
06.11.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 06.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Sprawdza bazy danych tylko do odczytu: PostgreSQL, MySQL, Redis, DynamoDB i RDS, pod kątem wolnych zapytań, indeksów i kosztów.

Wyzwalacze z opisu

review my databaseslow queriesmissing indexesunused indexesPostgres reviewMySQL reviewRedis reviewDynamoDB review
Oryginalny opis (EN)

Read-only database review for PostgreSQL, MySQL/MariaDB, Redis, DynamoDB, RDS/Aurora and SQLite. Use for "review my database", "slow queries", "missing indexes", "unused indexes", "Postgres review", "MySQL review", "Redis review", "DynamoDB review", "is this migration safe", "RDS/Aurora backups", "connection pool exhausted", "table bloat", "database costs too much".

Jak działa

  1. 1. Read the contract
  2. 2. Detect engines
  3. 3. Live consent
  4. 4. Work through the checklist
  5. 5. Write the report
Sekcje z nagłówków SKILL.md, w oryginale · 108 linii, 844 słów
Podgląd SKILL.md
---
name: database-review
description: Read-only database review for PostgreSQL, MySQL/MariaDB, Redis, DynamoDB, RDS/Aurora and SQLite. Use for "review my database", "slow queries", "missing indexes", "unused indexes", "Postgres review", "MySQL review", "Redis review", "DynamoDB review", "is this migration safe", "RDS/Aurora backups", "connection pool exhausted", "table bloat", "database costs too much".
hooks:
  PreToolUse:
    - matcher: Bash
      hooks:
        - type: command
          command: 'for f in "${CLAUDE_PLUGIN_ROOT}/skills/raystack/hooks/readonly-guard.sh" "${CLAUDE_PLUGIN_ROOT}/../raystack/hooks/readonly-guard.sh" "$HOME/.claude/skills/raystack/hooks/readonly-guard.sh"; do [ -x "$f" ] && exec "$f"; done; echo "RayStack review is read-only: guard missing" >&2; exit 2'
---

# Database review

Find what will hurt this database: slow or unindexed queries, unsafe migrations, missing
backups, connection exhaustion, bloat, wasted spend. Read-only. The output is a ranked
findings report.

## 1. Read the contract

Read `../raystack/references/review-contract.md` first and follow it. It covers inputs,
live consent, the read-only rules, questions, the report format and the no-client-data
rule. This file only adds what is specific to databases.

## 2. Detect engines

Scan the repo before asking anything. Review only the sections of the checklist that match.

| Engine | Signals |
|---|---|
| PostgreSQL | `postgres` image in compose, `DB_CONNECTION=pgsql`, `postgres://` URLs, `pg`/`psycopg`/`sqlx`/`asyncpg` deps, `engine = "postgres"` or `aurora-postgresql` in IaC |
| MySQL/MariaDB | `mysql`/`mariadb` image, `DB_CONNECTION=mysql`, `mysql2`/`pymysql` deps, `engine = "mysql"` or `aurora-mysql` |
| Redis | `redis`/`valkey` image, `REDIS_URL`, `CACHE_STORE=redis`, `aws_elasticache_*`, `AWS::ElastiCache::*` |
| DynamoDB | `aws_dynamodb_table`, `AWS::DynamoDB::Table`, `dynamodb.Table` (CDK), `client-dynamodb`, boto3 `dynamodb` |
| RDS/Aurora | `aws_db_instance`, `aws_rds_cluster`, `AWS::RDS::*`, `rds.DatabaseInstance`/`DatabaseCluster` (CDK) |
| SQLite | `DB_CONNECTION=sqlite`, `*.sqlite`/`*.db` files, `sqlite3` deps |
| Migrations | `database/migrations`, `db/migrate`, `migrations/`, `prisma/migrations`, `alembic/versions`, `drizzle/` |

One grep finds most of them:

`grep -rliE 'postgres|mysq|mariad|redis|valkey|dynamodb|aws_db_instance|aws_rds_cluster|elasticache|sqlite' --exclude-dir=node_modules --exclude-dir=vendor --exclude-dir=.git .`

Also note:
- which services connect to the DB and how (web, workers, scheduler, Lambda), and the
  pool size each one uses
- which DB CI tests against (SQLite in CI while production runs Postgres is a finding)
- whether any service runs migrations on boot

## 3. Live consent

Ask once, per the contract, in one batched question, each item unless the router passed it:
- which databases to inspect (connection env or host, database name) and which AWS profile
  and region for RDS/Aurora, DynamoDB and ElastiCache
- whether a read replica or staging copy exists. Prefer it over the primary
- whether read-only live access is OK at all

Never connect to a production database without live access Yes and the user's explicit yes
to that database. A database named in the router's Targets answer counts as that yes, but
only when live access was also Yes.
Recommend, before any call:
- PostgreSQL: a login role granted only `pg_monitor` (stats and settings, no table data),
  and prefix every psql call with `PGOPTIONS=-cdefault_transaction_read_only=on`
- MySQL/MariaDB: a user with only `PROCESS` and `SELECT` on `performance_schema.*`,
  `sys.*` and `information_schema.*`
- Redis: an ACL user with an explicit allow-list, no data reads:
  `-@all +info +slowlog|get +latency|doctor +memory|doctor +config|get +dbsize +client|list`
- AWS: `ReadOnlyAccess` or `ViewOnlyAccess`

Command shapes that pass the guard:
- `PGOPTIONS=-cdefault_transaction_read_only=on psql -X -c "select ..."`
- `mysql -e "select ..."` or `mysql -e "show ..."`
- `redis-cli INFO memory`
- `sqlite3 -readonly app.db "pragma integrity_check"`

Rules for SQL: one statement per command, wrap it in double quotes, use single quotes for
literals, no `$`, no backslashes, no `;`, no `/*` comments. Only functions on the guard's
read-only list work (`count`, `sum`, `round`, `substring`, `age`, `now`, `pg_size_pretty`,
`pg_relation_size`, ...). If a query needs another function, rewrite it or put it in
"Commands for you to run". `explain analyze` runs the query: use it only on a replica or
staging, only for reads, and only after consent. Plain `explain` needs `SELECT` on the table,
which the monitoring role lacks: ask the user to run it, or to grant `SELECT` on those tables.

An empty result or an error (view missing, feature off, no privilege) means "unavailable",
never "no problems". Say so under "Inputs used / missing" and use the item's fallback.

If live access is declined, review IaC, migrations and code, and list the exact queries
from the checklist under "Commands for you to run".

## 4. Work through the checklist

Open `references/checklist.md`. For each detected engine, take every item:
1. Collect the evidence: the grep over migrations/IaC/code, and the live query if allowed.
2. Decide if it is a finding. Judge "big table" from real row counts and sizes, not names.
3. Write the finding with evidence, why it matters, the fix as a diff or a command for the
   human, and Est. $/mo with arithmetic.

Migration review works fully offline. Read every pending or recent migration and flag:
- ALTERs that take a long exclusive lock or rewrite the table
- index builds that are not `CONCURRENTLY` (Postgres) or not online (MySQL)
- backfills in the same transaction as the schema change
- `NOT NULL` without a default on a big table
- destructive changes (drop, rename, truncate) without an expand/contract plan and a
  stated rollback path

Severity guide:
- **Critical**: data loss or outage is likely (no backups, wraparound near, a migration that
  locks a hot table, a production DB reachable from the internet)
- **High**: an outage under normal growth (pool exhaustion, a missing index on a hot path,
  replication slot filling the disk)
- **Medium**: slow paths, bloat, waste over $50/mo
- **Low**: hygiene

## 5. Write the report

Write the report per the contract with skill name `database-review`, at
`reviews/YYYY-MM-DD-database-review.md`. Name each database and engine version you
inspected under "Inputs used". Put every write the user must run (index builds, `VACUUM`,
`ALTER`, config changes, `redis-cli --bigkeys`) in "Commands for you to run".
Pliki w paczce (2)
  • SKILL.md 6 KB
  • references/checklist.md 46 KB

Wersje

W bazie nie ma innych skilli o nazwie database-review.

Migawka bazy z 13.11.2026 · wersja paczki e3d278351099 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 90database-designer
    Projektuje bazy danych z analizą schematu, optymalizacją indeksów i generowaniem migracji dla PostgreSQL, MySQL, MongoDB i DynamoDB oraz analizuje wydajność bazy.
  • 100database-reliability
    Prowadzi niezawodnie bazy PostgreSQL, MySQL, Redis, MongoDB, Kafkę, RDS, Aurora i Cloud SQL: przełączanie awaryjne, kopie, PITR, ćwiczenia odtwarzania i migracje.
  • 100aws-rds-spring-boot-integration
    Konfiguruje AWS RDS (Aurora, MySQL, PostgreSQL) w aplikacjach Spring Boot: pule HikariCP, rozdzielenie odczytu i zapisu, uwierzytelnianie IAM, połączenia SSL i integracja z Secrets Manager.
  • 90database-engineer
    Projektuje architekturę baz, optymalizuje schematy i zapytania oraz przygotowuje migracje w PostgreSQL, MySQL, MongoDB i Redis.
  • 100db-index-advisor
    Doradza w optymalizacji indeksów PostgreSQL, MySQL i SQLite: analizuje wolne zapytania, brakujące, nieużywane i nadmiarowe indeksy oraz generuje instrukcje CREATE INDEX z szacunkami EXPLAIN ANALYZE.
  • 100database
    Pomaga w architekturze baz danych, strojeniu MariaDB i MySQL, strategiach indeksowania, wolnych zapytaniach i wzorcach wielu połączeń.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.