kinfra-onboard

Onboard projects to Docker sandbox isolation and shared observability infrastructure.

2|1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/kpiteira/devops-ai --skill kinfra-onboard-kpiteira
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kinfra-onboard
Source: https://github.com/kpiteira/devops-ai/tree/main/skills/kinfra-onboard
Command: npx skills add https://github.com/kpiteira/devops-ai --skill kinfra-onboard-kpiteira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a project for sandboxed development with Docker Compose isolation, shared observability (Jaeger/Grafana/Prometheus), and quality infrastructure is a multi-step, error-prone process. This Skill automates the entire onboarding workflow with analysis, preview, execution, and verification phases. ## Core Features & Use Cases - Four-Phase Onboarding: Analyze the project state, propose changes for approval, execute modifications, then verify and commit with automatic rollback on failure. - Compose & OTEL Rewiring: Detects local observability services in docker-compose files, replaces them with the shared stack, and updates OTEL endpoints to the shared collector. - Quality Infrastructure Generation: Auto-detects test and lint commands from pyproject.toml, package.json, go.mod, or Cargo.toml to generate Makefiles, pre-commit hooks, and CI workflows. - Use Case: You have a Python project with a docker-compose.yml containing its own Jaeger container. Run the onboarding to get a sandbox-ready infra.toml, shared observability wiring, and CI quality gates in one guided flow. ## Quick Start Ask the assistant to onboard this project to the kinfra sandbox and observability ecosystem, starting with a read-only status check.

Frequently Asked Questions about kinfra-onboard

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

FAQPage Schema
How do I onboard a project to a Docker sandbox with observability?

Run the kinfra-onboard workflow, which analyzes your compose file and project config, proposes changes for approval, then executes kinfra init to create infra.toml, rewire observability services, and generate quality infrastructure.

How to migrate from a local Jaeger container to a shared observability stack?

The onboarding detects Jaeger, Prometheus, and Grafana services in your compose file, comments them out, and updates OTEL endpoints to the shared stack at localhost:44317. Sandbox containers receive the endpoint via an environment variable automatically.

Can I preview onboarding changes before modifying my project?

Yes, use the --check flag to run only the read-only analysis phase, which reports project state without changing files. The full workflow also includes a Propose phase that shows a dry-run plan and waits for explicit approval.

What happens if kinfra onboarding fails partway through?

The verification phase validates infra.toml, compose YAML, and quality checks. On failure it performs a full rollback: restoring the compose backup, deleting infra.toml, and reverting edited files with git checkout.

Does kinfra onboarding work without a docker-compose file?

Yes, projects without a compose file can use a worktree-only setup. The workflow offers a minimal infra.toml with has_sandbox set to false instead of sandbox isolation.