skills.rest
ohsonerdy
ohsonerdyCOMMUNITY
Explore all skills by this author →
GitHub

local-dev-environment

Design and audit reproducible local development workflows with pinned toolchains and secret bootstrap plans.

Updated Aug 27, 2026
Search Tags:#onboarding#development environment#docker#devcontainer#dependency pinning#CI parity#secret bootstrap
One-click install
npx skills add https://github.com/ohsonerdy/openclaw-frontier-stack --skill local-dev-environment-ohsonerdy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: local-dev-environment
Source: https://github.com/ohsonerdy/openclaw-frontier-stack/tree/main/skills/local-dev-environment
Command: npx skills add https://github.com/ohsonerdy/openclaw-frontier-stack --skill local-dev-environment-ohsonerdy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams eliminate “works on my machine” onboarding failures by designing and continuously maintaining a development environment that reliably gets engineers from a fresh checkout to their first PR within a measurable time budget.

Core Features & Use Cases

  • Dev-environment level selection (1–4): Choose the right parity-with-prod approach (toolchain pinning, containerized services, docker-compose full stack, or devcontainer/remote workspace) and avoid accidentally mixing levels.
  • Fresh-join audit and benchmark: Run a “what’s missing for someone joining today” audit, classify friction (blocking/major/minor), and measure time-to-first-PR using a stopwatch.
  • Secret bootstrap discipline: Replace unsafe secret-sharing patterns with a documented .env.example plus a precise retrieval path and fail-fast validation at startup.

Use this when a new hire spends a day or more setting up, when Docker/devcontainer onboarding documentation has drifted, or when CI and local dev disagree due to unpinned tool versions.

Quick Start

Ask the AI to redesign your repo’s local development setup by running a fresh-checkout onboarding audit, pinning versions for parity with CI, and producing an actionable plan to reach your target time-to-first-PR.

Frequently Asked Questions about local-dev-environment

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

FAQPage Schema
How do I fix "works on my machine" onboarding failures caused by Docker and devcontainer drift?▼

Fix onboarding failures by auditing your local development environment for toolchain and service divergences, then pinning versions to match CI and updating devcontainer configurations to restore parity. This eliminates setup friction for new engineers.

What's the best way to reduce engineer time-to-first-PR during onboarding?▼

Reduce time-to-first-PR by running a fresh-checkout onboarding audit to classify friction points as blocking, major, or minor, then applying dependency pinning and environment parity checks to reliably hit a targeted setup time budget.

How do I securely bootstrap local development secrets without sharing credentials in chat?▼

Securely bootstrap development secrets by creating a documented .env.example file with a precise retrieval path and fail-fast validation at startup, replacing unsafe secret-sharing patterns with a controlled, auditable access workflow.

When do I need a devcontainer versus docker-compose for my local development environment?▼

Choose a devcontainer for a fully remote workspace experience, or use docker-compose when containerizing full-stack services; selecting the right parity level prevents accidentally mixing toolchain pinning approaches and causing environment drift.

Why does my CI pipeline pass but my local dev environment fails?▼

CI and local dev environments disagree due to unpinned tool versions and undocumented service dependencies; fixing this requires enforcing dependency pinning and running parity checks to align local configurations with CI expectations.

Can I use a local development environment audit for a repository with existing Docker setup?▼

Yes, you can audit an existing Docker setup by measuring the current fresh-checkout time benchmark, classifying documented friction points, and applying guardrails to prevent future documentation and environment drift.

Related Skills

Explore More Software Engineering Skills→
X-School-AcademyX-School-Academy
9

dev-swarm-nodejs

Install and configure Node.js development environment with nvm and pnpm.

Official
Advanced
robotijnrobotijn
3

onboarding-validator

Audit developer onboarding workflows for setup friction and documentation gaps.

Community
Advanced
matt-rileymatt-riley
1

go-build-and-test

Diagnose Go build and test failures from toolchain or environment mismatches.

Community
Advanced
JaiminVadadoriyaJaiminVadadoriya
1

test-environments

Design and manage Docker Compose test environments with seed data and parity.

Community
Advanced