improve(agent): modernize database-architect agent

[davila7]

Summary

Automated review cycle for the database-architect agent — the #9 trending agent (300 downloads/week, 6,128 total). Located at cli-tool/components/agents/database/database-architect.md.

Improvements applied (8 total)

Critical fixes:

• Removed hardcoded 'strong_password' from PostgreSQL replication example — replaced with psql variable syntax (:'REPLICATOR_PASSWORD') and .pgpass guidance
• Fixed deprecated PostgreSQL config: recovery.conf → standby.signal + postgresql.conf settings (PG 12+); wal_keep_segments → wal_keep_size (PG 13+)

High-priority additions:

• Added Glob and Grep to tools list (standard in all peer agents)
• Added vector/AI database section covering pgvector with HNSW indexing, hybrid search, and decision matrix for dedicated vector DBs
• Added serverless/cloud-native database category: Neon, Supabase, PlanetScale, Turso with connection pattern differences
• Added connection pooling section: PgBouncer config, pool sizing formula, serverless function guidance

Medium-priority improvements:

• Replaced custom Python migration runner with standard tooling guidance (Flyway, Alembic, Prisma Migrate, Drizzle Kit, Atlas)
• Replaced MD5 with SHA-256 in sharding hash function

Stats

• 96 insertions, 81 deletions (net +15 lines — focused on replacing outdated content, not bloating)
• Validated by component-reviewer agent: APPROVED

Test plan

• Verify YAML frontmatter is valid (name, description, tools, model fields present)
• Confirm no hardcoded passwords remain in the file
• Check that deprecated PostgreSQL config (recovery.conf, wal_keep_segments, standby_mode) is removed
• Verify new sections render correctly in markdown (vector DB, serverless, connection pooling, migration tools)

---

Summary by cubic

Modernizes the database-architect agent with secure Postgres examples and up-to-date 2025 database patterns. Adds vector and serverless guidance, improves connection pooling, and aligns tooling with peers.

• Area: components (cli-tool/components/agents/database/database-architect.md)
• No new components; no catalog regen needed. No new env vars or secrets required.
• Security and Postgres updates: remove hardcoded password (use psql vars/.pgpass); replace recovery.conf with standby.signal; wal_keep_segments → wal_keep_size.
• New guidance: vector/AI with pgvector (HNSW, hybrid search), serverless DBs (Neon, Supabase, PlanetScale, Turso), and PgBouncer transaction-mode pooling for serverless.
• Tooling: add Glob and Grep, set model: sonnet, replace custom migration runner with Flyway/Alembic/Prisma/Drizzle/Atlas; switch sharding hash from MD5 to SHA‑256 with vnode note.

^{Written for commit 1212baa. Summary will update on new commits.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
aitmpl-dashboard	Ready	Preview, Comment	Apr 18, 2026 10:56pm
claude-code-templates	Ready	Preview, Comment	Apr 18, 2026 10:56pm

[github-actions]

👋 Thanks for contributing, @davila7!

This PR touches cli-tool/components/** and has been marked review-pending.

What happens next

1. 🤖 Automated security audit runs and posts results on this PR.
2. 👀 Maintainer review — a human reviewer validates the component with the component-reviewer agent (format, naming, security, clarity).
3. ✅ Merge — once approved, your PR is merged to main.
4. 📦 Catalog regeneration — the component catalog is rebuilt automatically.
5. 🚀 Live on aitmpl.com — your component appears on the website after deploy.

While you wait

• Check the Security Audit comment below for any issues to fix.
• Make sure your component follows the contribution guide.

This is an automated message. No action is required from you right now — a maintainer will review soon.

[github-actions]

⚠️ Security Audit Report

Status: ❌ FAILED

Metric	Count
Total Components	762
✅ Passed	360
❌ Failed	402
⚠️ Warnings	1007

❌ Failed Components (Top 5)

Component	Errors	Warnings	Score
vercel-edge-function	3	4	81/100
prompt-engineer	2	0	90/100
neon-expert	2	2	88/100
agent-overview	2	1	89/100
unused-code-cleaner	2	1	89/100

...and 397 more failed component(s)

---

📊 View Full Report for detailed error messages and all components

[cubic-dev-ai]

2 issues found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="cli-tool/components/agents/database/database-architect.md">

<violation number="1" location="cli-tool/components/agents/database/database-architect.md:335">
P2: The Flyway example mixes `CREATE INDEX CONCURRENTLY` into an atomic migration, which can fail under Flyway’s transactional execution for PostgreSQL.</violation>

<violation number="2" location="cli-tool/components/agents/database/database-architect.md:536">
P2: This SQL example is syntactically invalid because `ts_rank(...)` uses a placeholder ellipsis in executable SQL.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

P2: This SQL example is syntactically invalid because ts_rank(...) uses a placeholder ellipsis in executable SQL.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At cli-tool/components/agents/database/database-architect.md, line 536:

<comment>This SQL example is syntactically invalid because `ts_rank(...)` uses a placeholder ellipsis in executable SQL.</comment>

<file context>
@@ -520,10 +510,35 @@ def recommend_database_technology(requirements):
+       embedding <=> $1::vector AS semantic_distance,
+       ts_rank(to_tsvector('english', content), query) AS keyword_rank
+FROM documents, plainto_tsquery('english', $2) query
+ORDER BY (embedding <=> $1::vector) * 0.7 + (1 - ts_rank(...)) * 0.3
+LIMIT 20;
+```
</file context>

Suggested change

	ORDER BY (embedding <=> $1::vector) * 0.7 + (1 - ts_rank(...)) * 0.3
	ORDER BY semantic_distance * 0.7 + (1 - keyword_rank) * 0.3

[sadhiin]

Hi @davila7,

This issue is valid. The ts_rank(...) ellipsis in the ORDER BY clause is a placeholder that would fail at runtime.

Fix: replace it with the keyword_rank alias already defined in the SELECT:

ORDER BY (embedding <=> $1::vector) * 0.7 + (1 - keyword_rank) * 0.3

Postgres supports alias references in ORDER BY arithmetic, so this is clean and valid.

[cubic-dev-ai]

P2: The Flyway example mixes CREATE INDEX CONCURRENTLY into an atomic migration, which can fail under Flyway’s transactional execution for PostgreSQL.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At cli-tool/components/agents/database/database-architect.md, line 335:

<comment>The Flyway example mixes `CREATE INDEX CONCURRENTLY` into an atomic migration, which can fail under Flyway’s transactional execution for PostgreSQL.</comment>

<file context>
@@ -316,97 +317,66 @@ class PolyglotPersistenceLayer:
+-- Flyway example: V2__add_customer_tier.sql
+-- Each file runs exactly once; failures halt the pipeline
+ALTER TABLE customers ADD COLUMN tier VARCHAR(20) NOT NULL DEFAULT 'standard';
+CREATE INDEX CONCURRENTLY idx_customers_tier ON customers (tier);

</file context>

</details>

<a href="https://www.cubic.dev/action/fix/violation/72918718-5133-4cba-9f17-1d3b0efd88ca" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true">
  <picture>
    <source media="(prefers-color-scheme: dark)" srcset="https://cubic.dev/buttons/fix-with-cubic-dark.svg">
    <source media="(prefers-color-scheme: light)" srcset="https://cubic.dev/buttons/fix-with-cubic-light.svg">
    <img alt="Fix with Cubic" src="https://cubic.dev/buttons/fix-with-cubic-dark.svg">
  </picture>
</a>