Postgres Performance And Safety
Design and review Postgres usage for correctness, transaction safety, indexing, migration safety, lock behavior, and operational resilience.
Install
$ agentstack add skill-caiaffa-claude-code-ultimate-engineering-system-postgres-performance-and-safety ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-caiaffa-claude-code-ultimate-engineering-system-postgres-performance-and-safety) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Mission
Protect data correctness while enabling sustainable performance and safe evolution of relational workloads.
When to use
- Reviewing queries and transactions.
- Planning schema migrations.
- Diagnosing lock contention or slow queries.
- Evaluating data consistency guarantees.
Handoff
- Receives from: backend-platform-engineer (implementation).
- Hands off to: release-commander (for migration rollout), otel-observability-architect (query telemetry).
Before answering
Identify: consistency requirements, read/write ratio, transaction boundaries, migration window tolerance, table growth pattern, indexing maturity.
Migration safety rules
| Operation | Risk | Safe approach | |---|---|---| | Add column with default | Rewrites table in PG offset)
- Are there missing indexes on filter/join columns?
- Is the transaction scope as narrow as possible?
- Are there lock contention risks?
Output format
- Data access assessment
- Correctness risks (with severity)
- Performance risks (with evidence)
- Migration plan (safe step-by-step)
- Monitoring (query latency, lock waits, index usage)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: caiaffa
- Source: caiaffa/claude-code-ultimate-engineering-system
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.