Repository navigation
A full TRIP now asks the discovery questions, then one question before pushing. Everything in between chains on its own.
Plan → implement → release, no gates
/TRIP-1-planchains into implementation by default once the Codex plan review approves.--reviewbrings back the approval question (implement now / stop here / rework). A CodexNEEDS_REWORKstill stops and asks.--yolois accepted and ignored.- TRIP-2 hands off to the release without asking once the Codex code review approves, after finishing any unchecked plan to-dos.
- TRIP-3 commits, tags and merges without asking. "Push to remote?" is the release's only question.
/TRIP-2-implementstill runs on its own for an existing plan, a resumed session, or a different model.
TRIP-3-release: 13 steps → 9
- No more week numbers. No week anchor at init, no week in file names or the changelog table. New files:
docs/2-changelog/vx.y.z.md,docs/3-code-review/CR_vx.y.z.md. - One changelog record per release: a row in
changelog_table.md(version + commit message) and the per-version file. The Changelog Summary section is gone. - README version bump folded into Documentation Sync.
- TRIP-hotfix writes a short changelog file (issue, fix, root cause) instead of a summary entry.
Fewer skills: 14 → 12
TRIP-reviewremoved. Itschecklist.mdandcr-template.mdnow live incodex-code-review/, which reads them from there; the Codex review loop is unchanged.TRIP-testremoved. Test commands, organization, priorities and the hard-to-test guidance live indocs/4-unit-tests/TESTING.md, which init generates and TRIP-2 already uses as the testing guide.- Tutorial step removed from TRIP-3 and init.
TRIP-upgrade: 469 → 263 lines
- Merge only. Installs older than 2.8.1 (no version stamp) are first brought to 2.8.4 by following v2.8.4's upgrade skill, then merged.
- New "Structural Changes" section for what a file merge cannot express: it moves the review checklist and template into
codex-code-review/from their old path, movesTRIP-testcontent intoTESTING.md, drops the Week column from existing changelog tables (old Changelog Summary sections are left untouched), and repoints project text that still mentions the retired skills.
⚠️ Upgrading
- Projects that heavily customized
TRIP-3-releasewill see merge conflicts there: the file was restructured. Re-apply the project's customizations inside the new steps. - Existing
wN_vx.y.z.mdchangelogs andCR_wN_vx.y.z.mdreviews keep their names.