Select the smallest useful Codex engineering workflow from this repository's existing skills. Use when a task spans multiple engineering concerns, the user is unsure which skill to invoke, or loading every specialist would waste context; return a recommendation only and do not execute the engineering task.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Use this explicit-only skill as an educational example of workflow routing. It is not part of the recommended installable catalog; prefer clear specialist descriptions and direct activation in normal work.
Recommend one entry skill and only the supporting skills that materially change the work. Do not perform the requested engineering task.
$engineering-loop for an end-to-end feature or defect;$test-software for test-only work;$review-code for review-only work;$review-security for security-only analysis;$orchestrate-engineering only for complex work with genuinely
independent workstreams.$build-frontend for rendered UI, client behavior, or accessibility;$build-backend for APIs, services, persistence, jobs, or integrations;$operate-devops for infrastructure, CI/CD, deployment, or operations.Use this format:
Start with: $skill-name
Add only if needed: $other-skill
Why: one sentence tied to the task
Suggested invocation: $skill-name <bounded request and done condition>
Omit Add only if needed when one skill is sufficient. Never recommend loading
the entire catalog by default.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Build or modify backend APIs, services, jobs, persistence, and integrations while preserving contracts, authorization, data integrity, and failure behavior. Use for server-side features, database changes, background processing, backend defects, and service refactors; do not use for frontend-only or infrastructure-only work.
The English summary is being prepared. Showing the original description.
Build or modify frontend interfaces using repository-native components while preserving accessibility, responsive behavior, state handling, and visual verification. Use for UI features, design implementation, forms, client-side defects, and frontend refactors; do not use for backend-only or infrastructure-only work.
The English summary is being prepared. Showing the original description.
Implement a repository code or configuration change through reproduction, focused checks, review, and evidence. Use for end-to-end features and fixes; not for explanation-only, review-only, research, content publishing, or production operations.
The English summary is being prepared. Showing the original description.
Review a small code or documentation change and return only evidence-backed correctness findings. Use in the Codex How To local plugin lab; do not modify files or post remote comments.
The English summary is being prepared. Showing the original description.
Maintain a review-first Markdown knowledge base for Codex practices with source provenance, engineering capture, citation-aware queries, explicit archive and promotion, and deterministic linting. Use when asked to capture a durable engineering lesson, ingest Codex research, query or archive what the repository knows, check wiki health, reconcile conflicting guidance, or promote verified knowledge.
The English summary is being prepared. Showing the original description.
Plan and implement infrastructure, CI/CD, container, deployment, observability, and operational configuration changes with least privilege, staged validation, and rollback awareness. Use for pipelines, infrastructure as code, Kubernetes, containers, release automation, monitoring, and production-readiness work; do not use to perform destructive production actions without explicit authorization.
The English summary is being prepared. Showing the original description.