extract-plan
01Command Codex
Read a technical document (TIB, RFC, design doc, etc.) and generate a Linear project plan with milestones and implementation issues from it.
Command Codex
Read a technical document (TIB, RFC, design doc, etc.) and generate a Linear project plan with milestones and implementation issues from it.
Command Codex
Create a draft PR (and a new branch if needed).
Command Codex
Generate a PR description for the current branch.
Command Codex
Apply fixes for unresolved PR review comments, resolve merge conflicts with the base branch, commit, push, resolve threads, and monitor CI. Optionally watches for new review comments and re-applies fixes automatically.
Command Codex
CI-mode pull request review. Posts an inline GitHub review with a formal APPROVE / REQUESTCHANGES verdict. Runs in GitHub Actions on a PR.
Command Codex
Local PR review. Posts an inline GitHub review as a COMMENT (never auto-approves or requests changes — leave that decision to humans). Optionally schedules a 2-minute watcher cron via --watch.
Command Codex
Pre-PR local code review. Output to terminal only — no GitHub interaction. Optionally apply fixes once with --fix, or loop review→fix→re-review with --goal until the review passes cleanly.
Command Codex
Verify if this codebase is affected by a dependency vulnerability (CVE, supply chain attack, compromised package, etc.).
Skill Claude CodeCodex
Shared multi-lens review dispatcher. Invoked indirectly by the /pr-review- commands and /pr-fix, never directly. Walks agents/, decides which apply via flags, fans out one sub-agent per match, aggregates findings. Supersedes the previous lib/pr-review-base.md dispatcher.
Agent Codex
Focus: the trust boundary that ships our code. CI runs with privileged tokens; releases push artifacts under the org's identity. A bad workflow merge can leak secrets, run attacker code on a maintainer's box, or publish a poisoned package. This persona reviews diffs that touch that surface.
Agent Codex
Code-level correctness inside the function bodies the diff touches. Authoritative rules live in AGENTS.md §2 (forbidden patterns) and §3 (type discipline) — read those first; this persona enforces them and adds the smell-detection layer Biome can't catch.
Agent Codex
Three concerns, one persona: JSDoc on code exports, Markdown docs that describe the code, and the cross-references that knit them together. When the diff changes what the code does, the docs that describe it must keep up; when the diff renames or moves a file, every pointer to it must be updated; when the spec changes…
Agent Codex
Focus: package boundaries, public surface and deprecation lifecycle, type/import discipline, NodeNext compatibility. The authoritative rules live in AGENTS.md §1 (Architecture), §2 (Forbidden patterns — rule 5: deep cross-package imports), §3 (Type discipline), §4 (Public API & packaging), and §7 (Releases &…
Agent Codex
Review from the protocol-facing SDK contract: does this diff still model Morpho exactly? Authoritative rules live in AGENTS.md §1 (single source of truth per ABI/address and Action/Entity layering), §5 (security invariants as tests), §7 (pin ABIs and addresses in-package), and package/nested AGENTS.md files such as…
Agent Codex
What this persona catches: typed errors that exist in the code but die silently before reaching the caller. Empty catch, unhandled promise rejections, return values dropped on the floor, dead branches the type-checker missed.
Agent Codex
The contract that keeps this repo's review system coherent and discoverable. The personas, the engine, and AGENTS.md §10 are a single inventory expressed in several files: a wrong frontmatter field makes an agent never fire; a one-sided inventory edit leaves §10 claiming a roster that no longer matches agents/; a new…
Agent Codex
Mechanical-style enforcement and changeset relevance. Authoritative rules live in AGENTS.md §7 (changeset gates) and §8 (code style). This persona flags violations of those rules — it does not restate them.
Agent Codex
Two questions, every time: is there a test for this code? and is it in the right place?
Agent Codex
The boundary between the SDK and the chain. Authoritative rules live in AGENTS.md §1 (the Action layer is pure encode-only, no state reads), §2 (typed errors), and §5 (security invariants — chainId validation, authorization, accounting, LLTV buffer, inflation-attack guard, deposit routing). The Action-layer rule and…
Instructions file CodexOpenCode
AGENTS.md instructions for morpho-org/sdks, covering engineering rules, 1. architecture, layering: one direction, no exceptions, modularity: one reason to exist and testability: pure cores, i/o at the edge.
Instructions file
Claude Code instructions for morpho-org/sdks, a project described as: Collection of SDKs to ease interactions with the Morpho protocol and Morpho Vaults.