DoclingOptimisation

Maintain a structured JSON history of project changes in .history/changes.json. Use this skill after making any medium-to-large changes to the codebase. This includes: new files, API changes, schema changes, dependency changes, config changes, refactors, Dockerfile changes, and significant bug fixes. Do NOT log formatting-only changes, typo fixes, or trivial single-line edits. When in doubt, log it.

Use this skill when creating or modifying Dockerfiles, docker-compose files, GitHub Actions workflows, or deployment pipelines. Triggers on: container builds, CI/CD configuration, deployment automation, Azure Container App Jobs, Docker Hub, or any mention of "Docker", "container", "GitHub Actions", "workflow", "CI/CD", "pipeline", "deploy", or "build".

Use this skill when working on branching, PRs, commits, or releases. Triggers on: branch naming, PR workflow, commit messages, release strategy, or mentions of "branch", "PR", "commit", "release", "versioning", "changelog", or "git workflow".

Use this skill when implementing logging, monitoring, timing, or diagnostics. Triggers on: logging setup, performance profiling, timing, stderr output, or mentions of "logging", "monitoring", "timing", "profiling", "observability", or "diagnostics".

Use this skill when working on credentials, secrets, environment variables, Docker security, or any security-related concern. Triggers on: secrets management, credential handling, Docker security, environment variables, or mentions of "security", "secrets", "credentials", "env vars", or "vulnerability".