From zero-review
Configures runnable dev environments for repositories using repo inspection, env-var discovery, Docker/local setup, and smoke-test evidence.
npx claudepluginhub a7um/zero-review --plugin zero-reviewThis skill uses the workspace's default tool permissions.
Use this skill when you need to turn a repository into a usable development or verification environment. The primary output is an environment contract that tells a human or downstream agent how to run commands in the configured environment. Smoke testing is required evidence that the environment works, but end-to-end product testing is a downstream consumer of this skill rather than the skill's...
Sets up local development environments using Docker Compose, devcontainers, Tilt/Skaffold, and one-command Makefiles for dev/prod parity and easy startup.
Guides developers through setting up dev environments: identifies tools like Node.js/Python/Docker, provides platform-specific installs (Homebrew/apt/Chocolatey), configs env vars, verifies setups. For new projects, onboarding, machine switches.
Creates/updates Dockerfiles, docker-compose.yml, and environment variables for Go, TypeScript, or Python API/worker/batch/CLI services after implementation, enabling consistent local dev and deployment.
Share bugs, ideas, or general feedback.
Use this skill when you need to turn a repository into a usable development or verification environment. The primary output is an environment contract that tells a human or downstream agent how to run commands in the configured environment. Smoke testing is required evidence that the environment works, but end-to-end product testing is a downstream consumer of this skill rather than the skill's core job.
environment.md, environment.json, and artifacts/command-log.txt in the output directory you create for the run.repo to the current workspace when no path or URL is named..dev-output/auto-env/<repo>-<timestamp>/, with an artifacts/ subdirectory..env.example, .env.sample, .env.template, or similardocker-compose.yml, compose.yml, Dockerfiles, devcontainer filespackage.json, pyproject.toml, requirements.txt, Cargo.toml, go.mod, Makefile, or justfilePATH, HOME, TERM, CI, DEBUG, NODE_ENV, and test-only variables unless the project explicitly requires them for startup..git, dependency caches, and build artifacts that make the environment useful.docker exec or docker run command to reuse it.--help, build/test startup, HTTP health check, or page load.Every completed Auto-env run should leave:
environment.mdenvironment.jsonartifacts/command-log.txtOptional artifacts such as screenshots, server logs, compose logs, or generated outputs should go under artifacts/ when they materially support the smoke-test result.
environment.mdUse this structure:
# Environment Report
Status: ready | partial | blocked
Repo: <path-or-url>
Goal: <environment goal>
## Summary
<short setup result>
## Setup
<commands, services, dependencies, images/containers, and workdir>
## Environment Variables
<required and optional variables, with missing values called out>
## Run Instructions
<shell command, exec command, service start command, ports, and entrypoint>
## Smoke Test
<command/evidence and result>
## Blockers
<missing prerequisites, credentials, ambiguity, or none>
environment.jsonCreate a machine-readable object with these top-level fields:
status: ready, partial, or blockedrepo: path or URL plus any tag/ref usedenvironment: setup strategy, workdir, services, image/container names, ports, and base image when relevantenvVars: required, optional, supplied, and missing variablescommands: setup commands, run commands, shell commands, and smoke-test commandsartifacts: paths to logs, screenshots, or other evidencesmokeTest: command, result, and evidence summaryrunInstructions: exact commands a human or downstream agent should use nextblockers: unresolved prerequisites or limitationsStatus meanings:
ready: environment configured and smoke-tested.partial: environment mostly configured but named limitations remain.blocked: setup could not proceed because prerequisites, credentials, Docker, or key decisions are missing.Be fast and targeted:
${VAR_NAME} patterns.In prompt-sensitive cases, ask for only the variables needed for the requested environment goal. Prefer local fakes or optional-service omission when that still yields a useful dev environment.
For Docker-based setup:
For a reusable image modeled after the original auto-env setup flow:
/workspace.Current workspace:
repo="."
goal="Configure this repo so I can run the CLI help"
output=".dev-output/auto-env/$(basename "$PWD")-$(date +%Y%m%d-%H%M%S)"
With injected env:
repo="."
env_vars=("DATABASE_URL=postgres://..." "OPENAI_API_KEY=...")
goal="Configure the web app and smoke-test startup"
With extra local code:
repo="."
extra_paths=(../plugin)
goal="Configure this app with the sibling plugin available"
See reference.md for run parameters, output contract details, and integration notes.