UNPKG

paqad-ai

Version:

Spec-driven development framework — AI agents that think before they type

github.com/Eliyce/paqad-ai

Eliyce/paqad-ai

54 lines (39 loc) • 2.48 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
--- name: database-design-review description: 'Reviews schema and migration changes for integrity and safety. Use when a request changes tables, constraints, nullability, data movement or migration order, even in a small code change.' metadata: model_tier: reasoning cacheable: 'true' output_format: markdown paqad-meta: skill.meta.yaml --- ## What It Does Reviews schema and migration changes for correctness, rollout safety, and maintainability, with findings split cleanly across correctness risk, migration safety risk, and performance risk. ## Use This When For any request that changes tables, constraints, nullability, data movement, or migration sequencing, even when the code change seems small. ## Inputs - Read the changed migrations and the closest database docs for the affected module first. - Read `runtime/capabilities/coding/checklists/database-review-20pt.md` and `references/database-review-rubric.md` before reviewing. - Read any query or index docs that justify the new schema shape. ## Procedure 1. Run `scripts/scan-migration-smells.sh <migration-files...>` to surface candidate hazards (destructive drops, NOT-NULL without default, renames without shim, type changes, table locks, data deletion). 2. Cross-reference each hit with `assets/safe-migration-rules.txt` to decide whether it's actually unsafe in this project's context. 3. Review schema design (cardinality, defaults, constraints, nullability) and index/FK coverage as judgment work. 4. Bucket findings into Correctness / Migration Safety / Performance per `assets/output.template.md`. 5. Validate with `scripts/lint-output.sh`. ## Output Contract - Return sections named `Correctness Risks`, `Migration Safety Risks`, and `Performance Risks`. - List each finding as one bullet with the exact schema element or migration involved. - If a bucket has no findings, write `<Bucket Name>: none` exactly. ## Escalate / Stop Conditions - Ask when data volume, deployment sequencing, or rollback expectations are required to judge safety. - Warn when a migration appears non-additive, irreversible, or likely to lock hot tables. - Do not wave through undocumented backfills or destructive column changes. ## Resources - `references/database-review-rubric.md` - `scripts/scan-migration-smells.sh` - `scripts/lint-output.sh` - `assets/output.template.md` - `assets/safe-migration-rules.txt` - `runtime/capabilities/coding/checklists/database-review-20pt.md` - `agents/openai.yaml`