npx claudepluginhub dev10x-guru/dev10x-claude --plugin Dev10xThis skill is limited to using the following tools:
This skill follows `references/task-orchestration.md` patterns.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
This skill follows references/task-orchestration.md patterns.
Create a task at invocation, mark completed when done:
REQUIRED: Create a task at invocation. Execute at startup:
TaskCreate(subject="Execute safe database query", activeForm="Querying database")Mark completed when done: TaskUpdate(taskId, status="completed")
Safe read-only psql wrapper with two layers of protection:
hooks/scripts/validate-sql.py) — blocks
non-SELECT queries before they reach psqlSET default_transaction_read_only = on
and read-only DB users / read-replica endpoints${CLAUDE_PLUGIN_ROOT}/skills/db-psql/scripts/db.sh <database> "<SQL>"
${CLAUDE_PLUGIN_ROOT}/skills/db-psql/scripts/db.sh <database> -f <file>
${CLAUDE_PLUGIN_ROOT}/skills/db-psql/scripts/db.sh --list
# WRONG — -c flag is not supported, triggers safety hook block
db.sh pp -c "SELECT ..."
# WRONG — stdin piping is not supported
echo "SELECT ..." | db.sh pp
# CORRECT — SQL as second positional argument in quotes
db.sh pp "SELECT ..."
psql (PostgreSQL client)uv -- Python package manager used by parse-databases.py
(pip install uv or brew install uv)secret-tool (libsecret-tools) -- only needed for keyring backendCreate databases.yaml in one of the discovered locations. The
db.sh script searches for config files in this order:
$DB_CONFIG environment variable (explicit path)skills/db-psql/databases.yaml)~/.claude/memory/Dev10x/databases.yaml (global, user-level)skills/*/databases.yaml)~/.claude/skills/*/databases.yaml)Example YAML with both backends:
databases:
my-prod:
label: "My App production (read-only)"
aliases: [mp]
backend: env
env_var: DB_MY_PRODUCTION_RO
my-staging:
label: "My App staging (read-only)"
aliases: [ms]
backend: keyring
keyring_service: claude-db
keyring_account: my-staging
Configure the connection string using the backend specified in
databases.yaml:
env backend — set the environment variable in your shell profile:
export DB_MY_PRODUCTION_RO="postgres://user:pass@host:5432/db"
keyring backend — store the DSN in the system keyring:
secret-tool store --label "claude-db my-staging" \
service claude-db account my-staging
The SQL validation hook (validate-sql.py) is automatically
registered via hooks/hooks.json when this plugin is installed.
No manual configuration needed.
If the PreToolUse hook blocks a non-SELECT query, tell the user:
This query modifies data and cannot be run through the read-only tool. Here's the SQL to run manually:
-- Run against: <alias> (<label>) <the blocked query>
REQUIRED: Always prefix SQL snippets with a target database comment when outputting SQL for manual execution. This prevents copy-paste errors where SQL intended for staging runs against production. The comment format is:
-- Run against: bs (backend-staging)
Never attempt to bypass the safety checks.
Dev10x:db for query planning and schema discoverytt:db) provide databases.yaml
with aliases and schema references