القائمة
Re-resolve the model registry by querying OpenAI Codex cache, Google AI API, and Oracle CLI. Use when models feel stale or after a major model release.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Generates a narrative walkthrough of AI-authored code changes. Use after implementation to explain what changed, why, and how it behaves.
Use when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing. Resolves the latest flagship model from the model registry.
Evaluate plugin commands, agents, and skills against Anthropic Constitution principles. Score alignment on reasoning-based vs rule-based instruction spectrum, identify improvement opportunities. Use when the user wants to audit, score, or review the quality of a command, agent, or skill — e.g. "review this skill", "audit this command", "is this agent well-written", "score this against constitutional principles", or "check this for rule-based patterns".
Grilling session that challenges a plan against the target repo's existing domain model, sharpens terminology, and updates CONTEXT.md + ADRs inline as decisions crystallise. Invoked by /sdlc:plan at step 3.5 to keep architecture aligned with documented language before the plan is drafted.
Post-merge cleanup workflow. Detects PR merge, switches to main, pulls latest, runs tests, and removes worktree if exists. Use after PR is merged to clean up.
Use when the user asks to run Gemini CLI for code review, plan review, or big context (>200k) processing. Ideal for comprehensive analysis requiring large context windows. Resolves the latest flagship model from the model registry.
| name | update-models |
| description | Re-resolve the model registry by querying OpenAI Codex cache, Google AI API, and Oracle CLI. Use when models feel stale or after a major model release. |
Refresh sdlc-plugin/config/model-registry.md — the single source of truth that codex / gemini / oracle skills read to pick flagship/fast/previous model IDs. The resolver script does the three-source query (Codex cache, Gemini API, Oracle CLI); your job is to invoke it, surface what changed, and flag downstream drift the script can't see.
~/.codex/config.toml is flagged when its model field no longer matches codex-flagship — otherwise the user's codex CLI keeps pinning a superseded model without knowing.Find the plugin via portable Glob (per OPUS §13 — absolute dev paths silently return empty when the plugin is installed elsewhere, and the script will then fail to find its own write target):
Glob(pattern: "**/sdlc-plugin/package.json", path: "~/.claude/plugins") → cd into the directory containing the match.bun run resolve-models. The script handles authentication, API pagination, visibility filtering, and the three-source merge. Don't re-implement any part of this from the CLI; fix the script if the output is wrong, not the output itself (§9 trust-the-tool).The --dry-run flag prints the would-be registry to stdout without writing — use it when the user wants to preview changes before committing the file.
Read the script output and the resulting config/model-registry.md. Show the user:
gpt-5.4 was codex-flagship, now codex-previous).Silent success ("done, registry updated") hides the signal the user ran this for. The diff is the product, not the write.
After a successful refresh, check ~/.codex/config.toml. If its model field doesn't match the new codex-flagship ID, tell the user — don't edit it for them. The codex config is the user's personal CLI pin, and they may be holding a prior model intentionally (cost, workflow lock, reproducibility). Name the drift; let them choose.
A partial registry (e.g., Codex resolved but Gemini API returned 401) is worse than a stale registry — it poisons codex/gemini skills with asymmetric staleness where one provider looks fresh and the other is silently frozen. If any of the three sources errors:
$ARGUMENTS