codex-skills

Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning

Use when receiving UAT feedback, bug reports, user testing results, stakeholder feedback, QA findings, or any batch of issues to investigate. Investigates each item BEFORE creating issues, classifies by type and priority, creates well-formed GitHub issues with proper project board integration.

MANDATORY for all work - the project board is THE source of truth. This skill provides verification functions and gates that other skills MUST call. No work proceeds without project board compliance.

Use for LARGE work requiring feature-level grouping. Creates epic tracking issues, manages related issues under a common label, tracks epic progress, and coordinates with milestones.

Use when the user wants to design Codex agent equivalents (specialized workers/profiles/prompt files), define triggering conditions, or build reusable agent prompts and validation tools.

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

Use when the user wants to create Codex workflow hooks (pre/post run gates, tool-use validators, stop checks) or needs guidance on hook scripts and hooks.json configuration.

Analyze and resolve Sentry comments on GitHub Pull Requests. Use this when asked to review or fix issues identified by Sentry in PR comments. Can review specific PRs by number or automatically find recent PRs with Sentry feedback.

Setup Sentry AI Agent Monitoring in any project. Use this when asked to add AI monitoring, track LLM calls, monitor AI agents, or instrument OpenAI/Anthropic/Vercel AI/LangChain/Google GenAI. Automatically detects installed AI SDKs and configures the appropriate Sentry integration.

Setup Sentry Logging in any project. Use this when asked to add Sentry logs, enable structured logging, setup console log capture, or integrate logging with Sentry. Supports JavaScript, TypeScript, Python, Ruby, React, Next.js, and other frameworks.

Setup Sentry Metrics in any project. Use this when asked to add Sentry metrics, track custom metrics, setup counters/gauges/distributions, or instrument application performance metrics. Supports JavaScript, TypeScript, Python, React, Next.js, and Node.js.

Setup Sentry Tracing (Performance Monitoring) in any project. Use this when asked to add performance monitoring, enable tracing, track transactions/spans, or instrument application performance. Supports JavaScript, TypeScript, Python, Ruby, React, Next.js, and Node.js.

Use when the user wants to create or refine Codex skills, improve skill descriptions, organize skill resources, or follow Codex skill best practices.

Use after implementing features - verifies each acceptance criterion with structured testing and posts verification reports to the GitHub issue

Use when API code changes (routes, endpoints, schemas). Enforces Swagger/OpenAPI sync. Pauses work if documentation has drifted, triggering documentation-audit skill.

Use after code review - implement ALL findings; any finding not fixed MUST have tracking issue created; no finding disappears without trace

Use when starting any work session - establishes autonomous operation mode, overriding token limits and time pressure to work until goal is achieved

Use when user requests autonomous operation across multiple issues. Orchestrates parallel workers, monitors progress, handles SLEEP/WAKE cycles, and works until scope is complete without user intervention.

Use before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creation from correct base

Use after creating PR - monitor CI pipeline, resolve failures cyclically until green or issue is identified as unresolvable

Use when committing code - ensures atomic, descriptive commits that leave the codebase in a merge-ready state at every point

Use when asked for an architecture blueprint or explicitly asked to run the code-architect subagent.

Use when asked to trace existing codepaths or explicitly asked to run the code-explorer subagent.

Use when explicitly asked to run the code-reviewer subagent or when another skill requires the code-reviewer agent card.

Use when asked to simplify recently changed code without changing behavior or explicitly asked to run the code-simplifier subagent.

Use when asked to review code comments for accuracy/quality or explicitly asked to run the comment-analyzer subagent.

Use after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until complete

Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity

MANDATORY when designing schemas, writing migrations, creating indexes, or making architectural database decisions - enforces PostgreSQL 18 best practices including AIO, UUIDv7, temporal constraints, and modern indexing strategies

Use when a review finding cannot be fixed in current PR - creates properly documented tracking issue with full context, linked to parent, following full issue-driven-development process

Use when documentation drift is detected. Comprehensively audits codebase and creates/updates Swagger, features docs, and general documentation to achieve full sync.

Use for development environment setup - create and maintain init scripts, run smoke tests, ensure consistent environment across sessions

Use when encountering failures - assess severity, preserve evidence, execute rollback decision tree, and verify post-recovery state

Use when user-facing features change. Ensures features documentation is updated. Pauses work if documentation has drifted, triggering documentation-audit skill.

Use when writing code, documentation, or comments - always use accessible and respectful terminology

Use for MASSIVE work requests requiring multi-epic planning. Creates research spikes, documents all unknowns and decisions, builds resumable architecture documents, and structures work into epics and milestones.

Use when writing code - ensure complete JSDoc, docstrings, and inline comments assuming documentation will be generated from code

IPv6 is THE first-class citizen. All code, tests, documentation, and configurations MUST be IPv6-first. IPv4 MAY be added only for legacy support as a second-class citizen.

Use when an issue is too large for a single task - breaks into linked sub-issues with full documentation, ensuring manageable work units

Use for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub issue tracking, proper branching, TDD, code review, and CI verification