checklist
25Skill Claude CodeCodex
A workflow that creates a checklist for judging whether a product requirement is complete, clear, and consistent. It treats the checklist like a unit test for the requirement itself, not for the finished code.
Skill Claude CodeCodex
A workflow that creates a checklist for judging whether a product requirement is complete, clear, and consistent. It treats the checklist like a unit test for the requirement itself, not for the finished code.
Skill Claude CodeCodex
A specification-clarification workflow that asks up to five targeted questions and records the answers in the active specification. It is intended to run before detailed design.
Skill Claude CodeCodex
Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.
Skill Claude CodeCodex
C++ coding standards based on the C++ Core Guidelines (isocpp.github.io). Use when writing, reviewing, or refactoring C++ code to enforce modern, safe, and idiomatic practices.
Skill Claude CodeCodex
Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.
Skill Claude CodeCodex
A setup step for starting feature work in Git, a tool that tracks code changes. It creates or reuses a branch and a matching changes/ folder with a spec.md file.
Skill Claude CodeCodex
A design step that identifies the logical parts of a feature, their responsibilities, relationships, and important data. These parts are business boundaries, such as a billing or account area.
Skill Claude CodeCodex
A design-analysis step that identifies which user-visible capabilities must change when a new scenario is introduced. It maps those capabilities to existing functions or marks them as additions, changes, references, or removals.
Skill Claude CodeCodex
A document-generation step that turns a system’s logical entities into interface contracts. An interface contract describes how something can be called, what it accepts and returns, how it fails, and whether it is for outside callers or internal cooperation.
Skill Claude CodeCodex
Skill "design" from ZTE-AICloud/Co-OmniSpec, covering design, 行为准则, 环境初始化, step 0.1 检查变量 and step 0.3 校验.
Skill Claude CodeCodex
Django security best practices, authentication, authorization, CSRF protection, SQL injection prevention, XSS prevention, and secure deployment configurations.
Skill Claude CodeCodex
A process for turning black-box end-to-end test cases into an implementation analysis, including the entry points, test doubles, data, and checks involved. End-to-end tests verify a feature through its user-facing flow rather than testing one function alone.
Skill Claude CodeCodex
A test-analysis and test-case design workflow for turning a software specification into a test report and black-box test cases. Black-box tests check a system through its inputs and outputs without relying on its internal code.
Skill Claude CodeCodex
A review step for end-to-end (E2E) test plans, which test a feature through the system as a user would. It checks an implementation analysis report and updates it with missing coverage, dependency failures, and test-data details.
Skill Claude CodeCodex
Evaluate code generation quality using third-party judge model metrics (ICE Score + Code Judge). Use this when the user needs to assess generated code quality, compare code outputs, or evaluate AI-generated code against requirements. This skill provides automated scoring for functional correctness, usefulness, and…
Skill Claude CodeCodex
A complete evaluation workflow that collects code changes from an SDD feature branch and sends them to a third-party model for quality assessment. SDD is a process for developing software from written specifications.
Skill Claude CodeCodex
A requirements-consistency review guide for comparing documents and, when needed, related code. It checks whether changes stay within scope, cover the requirements, and use consistent meanings.
Skill Claude CodeCodex
A quality checker for design.md documents, which describe a proposed software design before implementation. It scores the document across structure, meaning, business rules, compliance, and writing quality, and lists specific bad cases it finds.
Skill Claude CodeCodex
A scoring guide for reviewing software specifications across business value, technical completeness, clarity and testability, and traceability. A software specification is a written description of what a system should do and how its requirements can be checked.
Skill Claude CodeCodex
FastAPI patterns for async APIs, dependency injection, Pydantic request and response models, OpenAPI docs, tests, security, and production readiness.
Skill Claude CodeCodex
Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.
Skill Claude CodeCodex
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
Skill Claude CodeCodex
An implementation workflow that carries out the tasks written in tasks.md according to a technical design. TDD, or test-driven development, means writing a failing test, making it pass, and then improving the code.
Skill Claude CodeCodex
A coverage report focused only on newly added or changed source files. Code coverage measures which parts of the code are exercised by tests, rather than checking the whole project.