mirror of
https://github.com/bestnite/quadlet-migrator-skill.git
synced 2026-04-03 22:53:28 +00:00
54376c4f6278b3c45e2987580a118e58afa79dc7
Clarify that generated artifacts should be reviewed in the current directory first, install.sh only places Quadlet units into the Quadlet target directory, and runtime support files must be copied to their correct host-side paths. Also strengthen the skill's pod-first, support-file discovery, and env completeness validation rules. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Quadlet Migrator
A skill for migrating docker run commands and Docker Compose-style deployments into maintainable Podman Quadlet units.
What it does
- translates
docker runand Compose-style inputs into Quadlet-oriented designs - writes generated artifacts to the current directory by default so they can be reviewed before being applied
- helps decide between
.container,.pod,.network,.volume, and.build, with a pod-first bias for multi-container services - preserves
.env/env_fileworkflows when appropriate - reduces large env templates into a small set of high-impact deployment questions
- can generate helper scripts with
install.shas the canonical apply step, plusreload.sh,start.sh,stop.sh, andrestart.sh - identifies required repo-local support files such as mounted config, init assets, and helper scripts that must ship with the result
- validates env completeness before claiming runnable output
- encourages explicit finalize and execution checklists for support files and env completeness
- explains rootless vs rootful apply targets, deployment notes, and validation steps
Design principles
- prefer the lightest operating mode that matches the request
- separate planning, review, and generation into explicit phases
- do not invent deployment-specific values
- make lossy mappings explicit
- prefer maintainable output over mechanical one-to-one translation
- default to review-first output in the current directory before installation
- prefer pod-first topology over preserving bridge networking when pod grouping expresses the intent cleanly
- copy runtime-required files to their correct host-side destinations, not just into the Quadlet unit directory
Operating modes
advice: explain mappings or review source inputs without writing final artifactsdesign: perform planning and finalize review, then stop before runnable artifact generationgenerate: produce approved runnable artifacts after planning and finalize review
References
SKILL.mdcontains the operating modes, workflow, and high-level rulesreferences/compose-mapping.mdcovers field mapping and topology decisionsreferences/env-strategy.mdcovers env handling, completeness validation, and typo detectionreferences/github-repo-intake.mdcovers repository discovery and canonical input selectionreferences/deployment-notes.mdcovers deployment guidancereferences/validation.mdcovers validation and troubleshooting
Limitations
This skill does not claim perfect equivalence between Docker Compose semantics and Podman Quadlet semantics.
License
MIT
Languages
Markdown
100%