ワンクリックで
reset-local-env
Reset the local Docker Compose development environment to a clean state (rebuild images, drop volumes).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Reset the local Docker Compose development environment to a clean state (rebuild images, drop volumes).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Generate and complete reusable security test documents under docs/security/ based on the current project implementation and/or a confirmed plan. Use when a developer asks to complete security test docs, add missing security scenarios, or establish a security test baseline for the project.
Generate and maintain reusable UI/UX test documents under docs/uiux/ based on the current project UI implementation and the design-system constraints. Use when a developer asks to complete UI/UX test docs, add missing UI/UX scenarios, align UI constraints, or wants UI consistency/a11y/responsive regression checks during development.
Guide for working with the Agent Orchestrator — a CLI tool for AI-native SDLC automation. Use when writing or editing YAML manifests (Workspace, Agent, Workflow, StepTemplate, ExecutionProfile, SecretStore, EnvStore, Trigger, CRD), running orchestrator CLI commands, designing workflow step pipelines, writing CEL prehook/finalize expressions, configuring triggers (cron/event-driven task creation), or configuring self-bootstrap workflows. Triggers: any mention of orchestrator config, YAML manifests with "orchestrator.dev/v2", workflow steps, prehooks, finalize rules, task create/start/pause, orchestrator run, step filtering, direct assembly, agent capabilities, StepTemplate prompts, execution profiles, sandbox configuration, secret management, or trigger/cron scheduling.
Govern feature request (FR) documents through their full lifecycle — from planning to implementation to closure. Use when the user asks to govern/治理 a feature request, close an FR, check FR status, or says "治理FR", "/fr-governance". Scans docs/feature_request/ for open FR docs, plans implementation, executes governance, and self-checks closure.
Generate or update QA/security/UIUX test documentation after confirmed feature implementation plans or completed refactors. Use this skill AFTER plan approval or code completion to: (1) add new QA test docs for new behavior, (2) generate design docs, and (3) run repo-wide cross-doc impact analysis (docs/qa/, docs/security/, docs/uiux/, docs/guide/ and its translations, docs/design_doc/, docs/showcases/, root Markdown including CHANGELOG.md, and .claude/skills/) to update stale steps, expectations, and assertions. Triggers when users ask to create QA docs, update test docs after implementation, or sync QA/security/UIUX docs after behavior changes.
Govern and periodically remediate QA documentation quality across docs/qa, docs/security, and docs/uiux. Use when users ask to audit QA docs, run recurring documentation checks, fix doc drift after refactors, enforce scenario limits/checklists/UI entry visibility, or synchronize README/manifest/changelog consistency.
| name | reset-local-env |
| description | Reset the local Docker Compose development environment to a clean state (rebuild images, drop volumes). |
Reset a local Docker Compose environment to a clean state.
Use this when:
Run the reset script to get a clean local environment:
./scripts/reset-docker.sh
This script performs:
This skill assumes the project was bootstrapped with project-bootstrap, which generates:
docker/docker-compose.ymlscripts/reset-docker.sh (calls Compose using docker/docker-compose.yml)cd /path/to/project
# Stop and remove containers
docker compose -f docker/docker-compose.yml down --remove-orphans
# Remove images
docker rmi <project>-core <project>-portal
# Remove volumes
docker volume ls
# Rebuild and start
docker compose -f docker/docker-compose.yml build --no-cache
docker compose -f docker/docker-compose.yml up -d
# Wait for services
sleep 30
docker compose -f docker/docker-compose.yml ps
Ports and credentials are project-specific. Use the generated docker/docker-compose.yml (and any .env) as the source of truth.
After reset, verify services are healthy:
# Check all containers are running
docker compose -f docker/docker-compose.yml ps
# If your services expose health endpoints, test them here.
# Example:
# curl http://localhost:8080/health
# Check logs
docker compose -f docker/docker-compose.yml logs
# Check specific service
docker logs <container-name>
# Check what's using the ports
lsof -i :3000
lsof -i :8080
lsof -i :4000
# Kill conflicting processes or change ports in docker-compose.yml
# Remove volumes with sudo if needed
docker volume ls
sudo docker volume rm <volume-name>