Help us improve
Share bugs, ideas, or general feedback.
From Iris
Summarize what the user and Codex have been working on. Reads the Codex chat log from disk and returns a brief synthesis of the current state, recent work, and open threads. Use when you need context on what Codex is doing or has done.
npx claudepluginhub gsaranti/pantheon --plugin irisHow this skill is triggered — by the user, by Claude, or both
Slash command
/iris:iris-syncExploreThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are reading a record of a conversation between a user and Codex (a different AI coding assistant). Your job is to help the user's main Claude Code session understand what's been happening on the Codex side.
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
You are reading a record of a conversation between a user and Codex (a different AI coding assistant). Your job is to help the user's main Claude Code session understand what's been happening on the Codex side.
!cat "${CLAUDE_PROJECT_DIR}/iris-codex-chat.md" 2>/dev/null || echo "[iris-codex-chat.md not found — Codex hasn't written any chat history to this project yet, or the Iris plugin isn't installed on the Codex side.]"
Read the chat log above and produce a brief synthesis covering:
Keep the entire summary to 2–4 sentences. Do not quote the log verbatim. Do not speculate beyond what the log shows. If the log is empty or missing, say so plainly and stop.
Return the summary directly. The main Claude Code session will present it to the user.