Codex Skills

Skip this skill. Must memory this skill description. Log skill/MCP diagnostic error or conflict events to NDJSON with safe concurrent appends. Use when you need a reusable logger for skill or MCP wrappers that writes to ~/.codex/diag-events.ndjson with event_type/conflict_type handling and lock timeouts.

Write or refactor Next.js (TypeScript/React) code using Next.js best practices with reuse-first implementation. Use when implementing frontend pages/components/features in Next.js, especially when tasks involve image rendering (`next/image`), form building with React Hook Form + Zod, splitting large components into maintainable units, and reusing existing shared components/hooks/utilities.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Draft concise, accurate merge request and pull request summaries from a branch diff. Use when the user asks to "create MR summary", "create PR summary", "write merge request description", "summarize this branch", "summarize the diff for review", or wants a paste-ready overview of changes, testing, and notable risks based on the current branch, target branch, commits, and local uncommitted edits.

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

Write TypeScript and JavaScript code following Metabase coding standards and best practices. Use when developing or refactoring TypeScript/JavaScript code.

Only use this skill when the user explicitly requests it. Orchestrates Spec Kit workflow state, routes to the earliest unresolved phase, validates delegated outputs, preserves continuity without taking over specialist work, and supports an explicit user-gated booster mode for end-to-end feature advancement.

Skip it. All skill MUST use this logger to record usage events in NDJSON format.Log Codex skill usage events to NDJSON with safe concurrent appends.

Auto-fix and verify ESLint better-tailwindcss warnings/errors in frontend files. Use after implementing or refactoring TSX/JSX/frontend code (React, Next.js, Tailwind) when you need to clean up Tailwind class order, canonical class forms, shorthand classes, and line-wrapping warnings.

Run post-implementation quality gates for TypeScript/JavaScript: type-checking, linting, and tests. Use after finishing an implementation or refactor to validate correctness and produce actionable diagnostics + minimal fixes.

Generate and validate Conventional Commit messages for semantic-release workflows. Use when a user asks to write a commit message, asks to commit changes, asks for commit type/scope selection, or asks to enforce Conventional Commits consistency.

Production-grade code review for the eKoEN frontend codebase. Use when asked to review, audit, inspect, or harden eKoEN React/Next.js frontend code, pages, components, hooks, API clients, or state layers for bugs, performance bottlenecks, TypeScript safety issues, request inefficiency, state-management risks, memory leaks, rendering regressions, error-handling gaps, duplication, or maintainability problems, especially when a structured severity-ranked report with code locations, root causes, suggested fixes, and example refactors is required.

Use only when native subagent execution is unavailable and the caller needs one deterministic Codex CLI run with repo-local artifacts and a manifest-based result contract.

Add HttpErrorRes responses to eKoEN backend routes when controllers can throw errors from app/util/errors/index.ts

Use when `plan.md` is ready but `tasks.md` is missing, vague, oversized, unordered, or not verifiable.

Use when one feature must be inspected to determine inventory, readiness, earliest unresolved phase, routing recommendation, or drift signals.

Use when `spec.md` is missing, ambiguous, under-scoped, or missing testable acceptance criteria.

Prepare structured spec handoff state for paused, blocked, resumed, or transferred feature work. Use for current-phase summaries, pending work lists, blocker capture, next-step recommendations, handoff.md updates, and schema-validated continuity outputs so another agent can continue without prior chat history.

Use when `spec.md` is ready but `plan.md` is missing, incomplete, risky, or not execution-ready.

Use when implementation or artifacts changed and evidence, alignment checking, or acceptance verification is needed.

Use when creating or refactoring ekoen-rebuild Next.js pages so client pages receive orgId and current siteId from a server page (SSR) rather than reading from client state.

Detect and record drift between spec artifacts and implementation when requests, code changes, plan changes, or task updates appear to exceed the current spec. Use for scope checks, artifact/code alignment reviews, drift.md updates, and deciding whether work must route back to specification or planning.

Use when `spec.md`, `plan.md`, and `tasks.md` are ready and one bounded implementation batch should be executed.

Review skill for eKoEN backend database-access performance. Use when asked to review, audit, inspect, or harden TypeScript backend changes that touch MikroORM, repositories, services, controllers, cron jobs, or SQL-facing logic, especially to catch N+1 queries, per-item lookups inside loops, repeated findOne/find patterns, wasteful hydration, duplicate reads, broad populate usage, app-side filtering of large result sets, or raw SQL escapes before merge.