database

Provision PostgreSQL databases and execute safe SQL queries across environments.

18|4|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/DevHive1/DevHive-Cli --skill database-devhive1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database
Source: https://github.com/DevHive1/DevHive-Cli/tree/main/skills/database
Command: npx skills add https://github.com/DevHive1/DevHive-Cli --skill database-devhive1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pg.

What problem does it solve?

This skill eliminates the complexity of manual database provisioning and the risk of executing unsafe SQL queries in production environments by providing a controlled, safety-checked interface.

Core Features & Use Cases

  • Database Lifecycle Management: Provision and verify PostgreSQL instances directly within the development environment.
  • Safe Query Execution: Run SQL queries with built-in protection against destructive commands and unauthorized production mutations.
  • Use Case: Use this skill to quickly inspect production data via read-only queries or to set up a new schema for a feature branch without leaving the terminal.

Quick Start

Use the database skill to check if the current project database is provisioned and then execute a select query to verify the users table.

Frequently Asked Questions about database

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute SQL queries on a PostgreSQL production database safely?

You can execute SQL queries on a PostgreSQL production database safely by enforcing read-only constraints on replicas and blocking destructive commands. This ensures data integrity while allowing secure data retrieval and schema management.

How do I provision a PostgreSQL database for a development environment?

Provisioning a PostgreSQL database for a development environment involves verifying and setting up instances directly within your workflow. This facilitates environment-specific database operations and schema management without requiring manual terminal commands.

Can I run destructive SQL commands during backend data management tasks?

You cannot run destructive SQL commands during backend data management tasks because the system blocks them to ensure data integrity. It enforces read-only constraints on production replicas to prevent unauthorized mutations.

What is the best way to inspect production data without risking accidental modifications?

The best way to inspect production data without risking accidental modifications is by using controlled, safety-checked read-only queries. This approach prevents destructive SQL commands from executing against the production database.

Does this database management approach support separate development and production environments?

Yes, this database management approach supports separate development and production environments. It manages PostgreSQL database provisioning and secure SQL query execution tailored to environment-specific database operations across both contexts.