local-dev-experience

Configure reproducible local development environments with docker-compose, Makefiles, devcontainers, and pre-commit hooks.

Updated Jun 25, 2026
One-click install
npx skills add https://github.com/oriddd/ai-toolkit --skill local-dev-experience-oriddd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-dev-experience
Source: https://github.com/oriddd/ai-toolkit/tree/main/copilot/public/skills/local-dev-experience
Command: npx skills add https://github.com/oriddd/ai-toolkit --skill local-dev-experience-oriddd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New contributors often lose hours figuring out how to run a repository locally. This Skill standardizes the inner development loop so any project can be started with a single make up && make test, eliminating manual setup of databases, brokers, and tooling. ## Core Features & Use Cases - Docker Compose for Dependencies: Mirrors production topology locally with pinned images for Postgres, Kafka, and MinIO, including healthchecks. - Canonical Makefile Targets: Defines shared verbs (up, down, build, test, it, lint, format, precommit, run, logs) so every project speaks the same commands. - Devcontainer & EditorConfig: Provisions VS Code / JetBrains Gateway environments via .devcontainer/devcontainer.json and pins formatting rules with .editorconfig. - Pre-commit Hooks: Runs formatting, linting, fast tests, and gitleaks secrets scanning before code is pushed. - Use Case: When scaffolding a new Spring Boot repository, apply this Skill to generate the compose file, Makefile, devcontainer, and pre-commit config so a new hire is productive within an hour. ## Quick Start Apply the local-dev-experience skill to this repository and generate the docker-compose file, Makefile, devcontainer config, and pre-commit hooks for my stack.

Frequently Asked Questions about local-dev-experience

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

FAQPage Schema
How do I set up a local development environment for a Spring Boot project?

Create a docker-compose.yml mirroring your downstream dependencies like Postgres and Kafka, then wrap it in Makefile targets such as `make up` and `make test`. Add a devcontainer.json so VS Code or JetBrains Gateway provisions the environment automatically.

What Makefile targets should every repository have?

Standard targets are up, down, build, test, it, lint, format, precommit, run, and logs. These shared verbs let contributors run any project without reading beyond the README, and `make` with no args lists available targets.

Should I use spring-boot-docker-compose or explicit make up?

Spring Boot 3.1+ can auto-start docker-compose.yml via the spring-boot-docker-compose dependency, which is convenient in dev mode. However, an explicit `make up` target is more predictable across different IDEs and CI pipelines.

How do I add secrets scanning to pre-commit hooks?

Add the gitleaks repository to your .pre-commit-config.yaml with a pinned revision such as v8.18.4. Combine it with formatting hooks like Spotless and fast unit tests, then install with `pre-commit install && pre-commit install --hook-type pre-push`.

Why should local development use containers instead of embedded databases?

Compose should mirror production topology with the same image families, such as postgres:16-alpine instead of embedded H2. This catches driver-specific behavior and configuration issues early rather than discovering them in staging or production.