dev-env

Generates linting, formatting, git hook, and monorepo configurations for development environments.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/medispis/opencode-config --skill dev-env-medispis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-env
Source: https://github.com/medispis/opencode-config/tree/main/skills/dev-env
Command: npx skills add https://github.com/medispis/opencode-config --skill dev-env-medispis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a consistent development environment requires manually configuring linters, formatters, type checkers, git hooks, and monorepo tooling across different ecosystems, which is repetitive and error-prone. ## Core Features & Use Cases - Tooling Setup: Detects the project's language, framework, and package manager, then generates configuration files for ESLint, Prettier, Ruff, golangci-lint, Clippy, and more, with matching install commands. - Environment Variable Documentation: Scans the codebase for environment variable usage patterns and produces a documented .env.example marking required versus optional variables. - Monorepo Configuration: Sets up Turborepo, Nx, Lerna, or pnpm workspaces with shared TypeScript, ESLint, and Prettier configs plus cached task pipelines. - Use Case: When bootstrapping a new TypeScript monorepo, use this Skill to generate turbo.json, a base tsconfig, shared lint configs, and a root .env.example in one pass. ## Quick Start Set up linting, formatting, git hooks, and a Turborepo monorepo structure for my Node.js project.

Frequently Asked Questions about dev-env

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

FAQPage Schema
How do I set up ESLint and Prettier for a new project?

Detect the package manager first, then install eslint, prettier, husky, and lint-staged as dev dependencies using npm or pnpm. Generate an `.eslintrc.js` for linting rules and a `.prettierrc` for formatting, and wire them into git hooks with husky.

Turborepo vs Nx vs Lerna: which monorepo tool should I use?

Turborepo fits most projects with a simple, low-complexity setup. Nx suits large teams with many packages and plugin needs but adds complexity. Lerna targets npm package publishing, while pnpm workspaces work for pnpm users with simple needs.

How do I generate a .env.example file from my codebase?

Scan the codebase for patterns like `process.env.X`, `os.environ["X"]`, and `env("X")` to find every variable in use. Document each one, mark required versus optional based on usage, and include realistic example values rather than placeholders.

Does this work with Python, Go, or Rust projects?

Yes, tooling setup covers multiple ecosystems. Python uses ruff, black, pre-commit, and mypy; Go uses golangci-lint; Rust uses clippy and rustfmt via rustup components. The install commands are matched to the detected language.

Will it overwrite my existing linting or workspace configuration?

No, the workflow detects existing setup before generating anything and asks before overwriting. If the project already uses workspaces, it enhances the current configuration rather than replacing it.