Skill Claude CodeCodex
A script that replaces the latest assistant response in a local conversation log with a generic agreement message. It supports Claude Code and Codex CLI session files.
Skill Claude Code
A change-checking skill that examines code edits, affected modules, tests, documentation, and the reason for the change. It treats a change as code plus the records needed to understand it later.
Skill Claude Code
A module-completeness checker that verifies a code module has the expected files, documentation, and tests. A module is a self-contained part of a larger software project.
Skill Claude Code
A code-quality checking skill that scans for complexity, repeated code, naming problems, and other code smells. Code smells are patterns that often make software harder to maintain.
Skill Claude Code
A security scanner that looks for dangerous coding patterns such as injection, exposed keys, unsafe file paths, cross-site scripting, and weak cryptography. It also checks whether security decisions are documented.
Cursor rule Cursor
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Skill Claude CodeCodex
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.
Skill Claude CodeCodex
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
Skill Claude CodeCodex
Use when you have a written implementation plan to execute in a separate session with review checkpoints.
Skill Claude CodeCodex
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
Skill Claude CodeCodex
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
Skill Claude CodeCodex
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
Skill Claude CodeCodex
Use when executing implementation plans with independent tasks in the current session.
Skill Claude CodeCodex
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
Skill Claude CodeCodex
Use when implementing any feature or bugfix, before writing implementation code.
Skill Claude CodeCodex
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions.
Skill Claude CodeCodex
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always.
Skill Claude CodeCodex
Use when you have a spec or requirements for a multi-step task, before touching code.
Skill Claude CodeCodex needs its repo
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
Skill Claude CodeCodex
Use when a service, frontend, or integration needs stable endpoint contracts, request and response schemas, error models, versioning, or interaction rules.
Skill Claude CodeCodex
Use when code purpose, module responsibilities, data flow, dependencies, or hidden assumptions need to be explained for onboarding, debugging, or safe changes.
Skill Claude CodeCodex
Use when requirements or designs are ready to be turned into production code for feature delivery, scaffolding, implementation gaps, or maintainable module creation.
Skill Claude CodeCodex
Use when existing code needs safer structural cleanup, duplication removal, modularization, or maintainability improvement without intentionally changing expected behavior.
Skill Claude CodeCodex
Use when changes need reviewer-style scrutiny for correctness, regression risk, maintainability, missing tests, or delivery readiness before merge or release.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: