Codex Check Repository Portability Before Committing Local Paths
Review changed docs, scripts, and examples for machine-specific paths and replace them with portable references.
中文Install in Codex
Use a local Git workspace and its changed files. Synthetic paths are enough for practice.
- Copy the pinned `.codex/skills/repo-portability-hygiene/` directory into `.agents/skills/repo-portability-hygiene/` in the project.
- Tell Codex the changed-file scope and ask it to scan for Windows and Unix local paths using the repository's conventions.
Example task
Put `C:/ExampleUser/demo/docs/start.md` and an external media path in a fixture. Replace them with `docs/start.md` and a documented `<asset-directory>` placeholder respectively.What to check
Public instructions no longer depend on the original workstation, and readers can distinguish repository paths from external inputs.
Original SKILL.md on GitHub · Updated
Frequently asked question
What if a public example needs an absolute path shape?
Use a generic placeholder and explain what type of path the reader should supply.