Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,16 @@
Headings are `## <repo version> — <what moved>`. Ports are named in the body with their own rev
counters: a port tracks the parent's layer structure, not its revision number.

## Unreleased

No policy or Claude Code plugin change; `stackwich-codex-rev` stays at 7.

### Fixed
- The Codex installer left Stackwich agents from an earlier revision in place on an upgrade. Step 4
now treats an agent carrying the Stackwich Codex credit as an earlier install and offers an
in-place refresh that keeps its `name` and model settings; step 5 checks it. Codex users pick it
up by copying `codex/` again. (#51)

## 3.6.1 — confirm agents without `/agents`

The policy is unchanged: `policy-rev` stays at 9 and there is nothing to re-run. Update the plugin
Expand Down
10 changes: 10 additions & 0 deletions codex/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,14 @@ matching `name` values. If a name belongs to an unrelated agent, ask for a repla
substitute it consistently in the policy block, filenames, TOML `name` values, descriptions,
and in-body references. Never overwrite an unrelated agent.

An existing agent file whose header comment is the Stackwich Codex credit (`# Created by
Abhirup Banerjee (@ovhirup) as part of the Stackwich Codex architecture.`) is an earlier
install, not a collision. Compare it with its template, with any rename applied and ignoring
`model` and `model_reasoning_effort`, which users may tune. If it differs, tell the user it is
out of date and offer to replace it in place, keeping its `name` and those model settings;
never overwrite it without asking. On an upgrade, offer this even if the user doesn't mention
agents.

Write standalone TOML files from the templates to the chosen agents directory. Do not pin
model names: the templates use reasoning and sandbox settings so they remain portable across
accounts and future model catalogs.
Expand All @@ -65,6 +73,8 @@ accounts and future model catalogs.

- Confirm there is exactly one opening marker and one closing marker in the target file.
- Parse every created agent TOML with Python's `tomllib` when Python 3.11+ is available.
- Every Stackwich agent written or kept matches its template apart from renames and model
settings, or the user chose to keep an older or edited one, and you say so.
- Inspect the resulting diff or changed paths and run `git diff --check` for project scope
when the target is in a Git repository.
- Verify behavior or structure rather than re-reading a just-written file solely to confirm
Expand Down
Loading