Coding standards, frameworks, refactoring, and code review (16.4K skills)
Migrate an existing Remotion video composition to HyperFrames HTML and GSAP animation. Check the source for unsupported patterns, translate compatible scenes, compare rendered videos for visual differences, and document anything that could not be preserved.
Create a GitHub pull request that follows the project's template. Review commits and changed files, gather issue and testing details, check branch readiness, and use the GitHub CLI to submit a regular or draft request.
Prepare a one-time What's new dialog for the desktop app when several meaningful features have accumulated. The skill selects changelog highlights, drafts concise copy, updates the content file, and guides testing and in-app previews.
Build interactive terminal screens with OpenTUI using its core API, React, or Solid. Guides framework selection, components, layout, keyboard input, animations, and testing, with references for project setup and troubleshooting.
Build AI agents with Cline SDK using guidance on choosing APIs, adding custom tools, saving sessions, and handling live events. References also cover model providers, scheduled runs, multi-agent coordination, and production deployment.
Apply strict coding practices to Python, Rust, TypeScript, and Go projects. The skill guides typed errors, handling every variant, resource management, and tests that verify observable behavior, while prioritizing reuse and minimal changes.
Research a coding task before implementation and turn it into a detailed work plan with decisions, dependencies, and verification steps. The plan is written after approval, while code changes remain a separate workflow.
Investigate LazyCodex and Codex bugs using reproduction results and source code. Identify the responsible repository, then prepare or submit an English GitHub report with evidence, likely causes, fix guidance, and a verification plan.
Compare current code with the latest published npm releases to identify unpublished changes. Read actual code differences, explain their impact across shared components and agent environments, and recommend version updates for each release layer.
Help Codex respond to automatic warnings about comments after code edits. It explains when the checker runs and directs Codex to fix the flagged comment or explain it before continuing with other work.
Take implementation work through small, independently mergeable pull requests. Use a separate working directory for each PR, record manual QA evidence, write English review descriptions, resolve CI and review findings, then merge and clean up.
Guides coding work from planning and implementation through checks on actual screens, commands, or APIs. It adjusts verification to the change’s risk and records evidence, decisions, and cleanup so completion can be assessed against the requested outcome.
Execute a written work plan by assigning implementation and verification to subagents. Track progress, isolate work in Git worktrees, record test evidence, and require independent verification before marking tasks complete, with optional pull request delivery.
Document a project's structure, commands, and specific conventions in a hierarchy of AGENTS.md files. Analyze directory complexity to choose useful locations, update existing guidance, and check that child files avoid repeating their parents.
Find unused TypeScript code, verify references with a language server, and assign removals to parallel agents. Group changes by file, create separate commits, and check types, tests, and the build after cleanup.
Explain tips shown in senpi or omo by checking the installed tip list, user settings, and implementation code. Learn what a feature actually does, why a tip appears, and which tips your setup can show.
Analyze all open GitHub issues and pull requests, then produce reports backed by links to specific code commits. Assess bugs, feature requests, and merge readiness without changing anything on GitHub.
Set up a language server, a tool that helps agents understand source code, for a project. Detect the language, install and configure the server, then verify that it responds to a diagnostic request.
Reproduce and fix LazyCodex or Codex defects in a temporary workspace. Verify the change with regression tests and real usage, then deliver an upstream Codex pull request or a LazyCodex issue containing the tested patch.
Guides code cleanup and restructuring by mapping dependencies, assessing test coverage, and planning small changes. Supports tasks such as extracting functions or renaming symbols, with checks after each step and recovery when verification fails.
Turn a broad coding request into a concrete work plan grounded in the codebase. After user approval, it documents affected files, decisions, dependencies, and verification steps so a separate worker can carry out the implementation.
Uses multiple agents with different critical roles to challenge assumptions, complexity, risks, and alternatives. Findings that withstand review go to a dedicated planner, who turns them into sequenced tasks with explicit success criteria.
Audit a codebase across nine areas, including architecture, tests, security, and documentation. Produces TECH_DEBT_AUDIT.md with source locations, severity ratings, estimated repair effort, and prioritized recommendations to help plan maintenance work.
Checks LazyCodex and Codex CLI installations against current source code, inspecting versions, settings, plugin files, and runtime behavior. Produces an evidence-backed health report with suggested fixes while leaving the installed setup unchanged.