Coding standards, frameworks, refactoring, and code review (16.5K skills)
Build and debug mods that change Claude’s interface or behavior. Add panels, status messages, slash commands, or hooks that respond to prompts and tool calls, with guidance for file structure, type checks, and behavior tests.
Create or improve a project-specific skill with verified build, launch, and interaction steps. Package concise instructions with scripts or existing command-line tools so future agents can run and exercise the application.
Analyze a codebase and create a CLAUDE.md guide for future Claude Code sessions. Capture build and test commands, explain the overall architecture, and incorporate relevant information from existing documentation and development rules.
Review code changes in a diff, pull request, branch, or file path to identify bugs and cleanup opportunities. Findings include file locations and concrete failure scenarios, with options to apply fixes or post comments.
Coordinate large migrations, refactors, and bulk renames by splitting them into independent tasks. After plan approval, 5–30 agents work in separate Git worktrees, isolated working directories, then review, test, and open a pull request for each task.
Review changed code from four angles: reuse, simplicity, efficiency, and whether fixes address the underlying mechanism. Applies suitable improvements within the reviewed scope while preserving intended behavior, and reports fixes or skipped findings.
Review a specified code change without editing files. Checks the full diff, surrounding code, tests, and callers to identify actionable defects introduced by the change, then reports findings by severity with file and line references.
Monitor a GitHub pull request for review feedback, automated check failures, and merge readiness. Diagnose failures, fix problems caused by the branch, and retry likely temporary failures while continuing to watch for updates.
Update pull request titles and descriptions to explain why a change matters and what it changes. Preserve existing images and important details, summarize relevant verification, and describe the correct scope for linked, dependent pull requests.
Update Codex's pinned V8 and rusty_v8 versions, synchronize build settings and checksums, and validate a release candidate. If validation fails, investigate upstream changes and adjust the affected build files to restore a working build.
Create a Codex plugin scaffold with a valid manifest, optional folders for skills and supporting files, and personal marketplace entries. Also guides validation and the cache refresh and reinstall steps used during local plugin development.
Assess whether a code change is small enough to review using line-count guidance. For larger changes, examine the actual differences, dependencies, and calling code to suggest reviewable stages and the smallest coherent first step.
Review external integration points for breaking changes that could disrupt existing use. Examine app-server APIs, command-line parameters, configuration loading, and session resumption from saved records, continuing beyond the first issue to cover possible failure paths.
Choose Rust types for operating system paths in Codex server protocols and internal code. Guides new definitions and explicitly requested migrations while preserving client compatibility and handling paths from different operating systems.
Review code that manages the conversation history and extra information sent to Codex models. Apply rules for incremental history, size limits, cache stability, manual review of large additions, and required implementation structures.
Run a final pull request review using separate agents for each available review skill. Collect all reported issues into a numbered Markdown list, with a specific file path and line number for every finding.
Create or update Codex skills with focused instructions and supporting files where needed. Organize reusable scripts, references, and output assets, clarify when the skill applies, and validate its structure without expanding the user's requested scope.
Write or refactor Remotion components so timing and full-size layout live on the content itself. Reduce redundant wrappers and organize related scenes or clips on shared Studio timeline rows while preserving timing and layout behavior.
Update Mediabunny and its related packages throughout Remotion, including templates, CLI version references, and the documentation compatibility table. The workflow checks the latest published version, aligns the relevant entries, and finishes by installing dependencies with Bun.
Bring a Remotion branch up to date with the official main branch while preserving local changes and published history. Handle temporary change storage, merges, conflicts, validation, and a normal push when requested.
Improve Remotion Studio rendering performance by limiting which components update with every frame. The skill guides on-demand timeline reads and React.memo usage, helping keep stable components from rerendering unnecessarily while preserving updates where the displayed frame matters.
Guide implementation and debugging of visual Sequence editing in Remotion Studio. It documents how sequence identifiers, node paths, and stack traces behave during hot reload, and suggests how to track expanded UI state.
Refresh the GitHub star count displayed on Remotion’s website. It checks GitHub, rounds the number down to the nearest thousand, updates three components, and commits and pushes the changes to main.
Upload preview images and videos for a Remotion Element to remotion.media, then update the corresponding URLs. The skill also handles local asset cleanup according to whether previews come from fresh renders or committed submissions.