local_dev

Automate local development setup with PostgreSQL and Python virtual environments.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/wesuuu/runbook --skill local-dev-wesuuu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local_dev
Source: https://github.com/wesuuu/runbook/tree/main/.agent/skills/local_dev
Command: npx skills add https://github.com/wesuuu/runbook --skill local-dev-wesuuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configuring and debugging a local development environment can be error-prone, especially when juggling native services, database connections, and process management.

Core Features & Use Cases

  • Native environment guidance: Use a Python virtual environment located at .venv and validate it's active before running commands.
  • Local database setup: Connect to a local PostgreSQL instance on localhost:5432 with standard credentials.
  • Process management: Provide commands and workflows to start, monitor, and restart local services without containerization.
  • Use Case: A developer wants to quickly verify connectivity to Postgres, run the API locally, and ensure all tools run in a clean environment.

Quick Start

Start by creating and activating the virtual environment at the project root, then verify the Postgres connection is reachable and your services can be launched natively.

Frequently Asked Questions about local_dev

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

FAQPage Schema
How do I set up a local development environment with PostgreSQL and Python without using containers?

To set up a local development environment without containers, create and activate a Python virtual environment at .venv, ensure a local PostgreSQL instance is running on localhost:5432, and use native process management workflows to start and monitor your services.

What is the standard workflow for managing local Python processes and database connections during native development?

The standard workflow for local development involves validating that your .venv virtual environment is active before running commands, verifying connectivity to your local PostgreSQL database, and executing provided commands to start, monitor, and restart native services.

Do I need Docker to run a local PostgreSQL database and Python virtual environment for development?

You do not need Docker, as this local development approach enforces native execution without containerization. It requires a locally available PostgreSQL instance on localhost:5432 and a Python virtual environment located at .venv for safe, isolated execution.

Can I use a different port or virtual environment path for my local PostgreSQL setup?

You cannot use a different port or path, as the setup strictly enforces a Python virtual environment at .venv and a local PostgreSQL instance specifically on localhost:5432 to ensure safe, isolated execution.

How do I verify my local PostgreSQL connection and start my API natively?

To verify your PostgreSQL connection and start your API natively, first activate the .venv virtual environment at your project root, then check that the local database on localhost:5432 is reachable, and finally launch your services using the provided native process management commands.