This repository is intentionally thin.
Keep changes focused on:
- install and uninstall ergonomics
- repository packaging
- skill quality
- diagnostics and validation
- documentation
Do not re-implement the native scheduler here. The scheduler belongs in the Codex fork that provides cron_create, cron_list, and cron_delete.
Run these before opening a pull request:
./scripts/doctor.sh
./scripts/smoke.shFor a release candidate, run:
./scripts/release-check.sh- Prefer native thread cron over automation for recurring work in the current thread.
- Keep install steps conservative and reversible.
- Do not silently override user config that explicitly disables plugins or this plugin.
- Keep docs short, specific, and operational.
Good pull requests usually do one of these:
- improve installation reliability
- improve README clarity or examples
- improve skill prompts or guardrails
- improve validation or release checks
If a change increases magic or hidden coupling, it is probably the wrong direction.