rebuild-docker

Detect changed files and rebuild only affected docker-compose services.

1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/samwang0723/kenjaku --skill rebuild-docker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rebuild-docker
Source: https://github.com/samwang0723/kenjaku/tree/main/.claude/skills/rebuild-docker
Command: npx skills add https://github.com/samwang0723/kenjaku --skill rebuild-docker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents long, unnecessary rebuilds by detecting which parts of a monorepo changed and rebuilding or restarting only the affected docker-compose services so developers avoid a full Rust workspace rebuild for static frontend edits.

Core Features & Use Cases

  • Change detection: Compares file modification times against container start times to determine what is newer.
  • Minimal actions: Chooses between rebuilding kenjaku, rebuilding geto-web with --no-deps, restarting kenjaku for config-only changes, or doing both in parallel.
  • Safety and verification: Avoids docker compose down that would drop data, prompts before slow Rust rebuilds, and verifies service health after deployment.
  • Use Case: Quickly redeploy a modified geto-web static asset without triggering a multi-minute Rust rebuild, or apply a schema migration safely by restarting the kenjaku service.

Quick Start

Run the rebuild-docker procedure to detect changed files and execute the minimal docker compose build, up, or restart required to update the running services.

Frequently Asked Questions about rebuild-docker

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

FAQPage Schema
How do I rebuild only changed Docker Compose services in a monorepo?

To rebuild only changed Docker Compose services, compare file modification times against container start times and execute minimal docker compose build, up, or restart commands for the affected services only.

How do I redeploy frontend changes without triggering a full Rust workspace rebuild?

Redeploy frontend changes without a full Rust workspace rebuild by detecting static asset modifications and rebuilding the frontend service with the --no-deps flag to isolate it from backend dependencies.

Why does Docker Compose rebuild everything when I only changed a frontend static asset?

Docker Compose rebuilds everything because standard commands lack change detection. Comparing file modification times to container start times lets you select minimal build or restart commands for only the affected services.

Does this Docker rebuild approach run docker compose down or drop my data?

This Docker rebuild approach avoids docker compose down entirely to prevent data loss. It selects safe build, up, or restart commands and verifies service health after deployment without destructive operations.

Can I restart a backend service for config-only changes without a slow Rust rebuild?

You can restart a backend service for config-only changes without a slow Rust rebuild. The process detects non-code modifications and issues a docker compose restart, prompting for confirmation before lengthy workspace rebuilds.