cli-tools

Provides operational reference for git, gh, pnpm, kubectl, jq, and other CLI tools used in agent sessions.

1|Updated Jul 15, 2026
One-click install
npx skills add https://github.com/stefanrusek/dark-harness --skill cli-tools-stefanrusek
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cli-tools
Source: https://github.com/stefanrusek/dark-harness/tree/main/src/prompt/skills/cli-tools
Command: npx skills add https://github.com/stefanrusek/dark-harness --skill cli-tools-stefanrusek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents working in unattended dark-factory sessions repeatedly need correct, safe usage patterns for domain-specific command-line tools, and guessing flags or workflows leads to broken commits, failed CI, or leaked secrets. ## Core Features & Use Cases - Version control and GitHub workflows: Covers git commit discipline, worktrees, shared-tree safety, and gh commands for PRs, issues, and CI logs. - Dev environment and cluster operations: Documents pnpm workspace commands, Tilt dev environments, and kubectl diagnostics with explicit namespace handling. - Data shaping, secrets, and HTTP: Explains jq filtering patterns, Doppler secret injection without exposing values, one-off npx/Playwright runs, and scripted curl requests. - Use Case: An agent needs to diagnose a failing CI check, pull the logs with gh run view, fix the issue in a pnpm monorepo, and open a PR — this reference gives the exact commands and safety rules for each step. ## Quick Start Ask the agent to consult the cli-tools reference before running git, gh, pnpm, tilt, kubectl, jq, doppler, npx, or curl commands in the current task.

Frequently Asked Questions about cli-tools

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

FAQPage Schema
How do I pull GitHub CI logs from the command line?▼

Use `gh run list` to find the workflow run, then `gh run view <id> --log` to pull the full CI logs directly instead of guessing why a check failed. `gh pr checks` shows status before merging.

How do I run pnpm commands in a monorepo workspace?▼

Use `pnpm -w` for workspace-root commands and `pnpm --filter <pkg>` to target a specific package. Use `pnpm exec <bin>` for locally installed binaries and `pnpm dlx <pkg>` for one-off runs without adding a dependency.

Should I use tilt up or tilt ci in an unattended environment?▼

Use `tilt ci` in unattended or dark-factory contexts because it runs resources to completion and exits, unlike the long-running `tilt up`. Use `tilt up --stream=true` or `tilt logs` when you need to follow output non-interactively.

How do I use secrets from Doppler without exposing them?▼

Use `doppler run -- <command>` to inject secrets as environment variables only for that command's duration, rather than exporting them into the shell. Never echo secret values into logs or commit them to files.

Why should kubectl commands always specify a namespace?▼

The default namespace from the current context can silently differ between environments, causing commands to target the wrong resources. Always pass `-n <namespace>` explicitly for get, logs, describe, and apply operations.

When is it unsafe to amend commits or force-push in git?▼

Never amend a commit another agent might be building on, and never force-push a shared branch — revert instead. In shared working trees, commit before yielding a turn so other agents can see your work.