Coding standards, frameworks, refactoring, and code review (14.8K skills)
Reduce changes on your own branch before opening or updating a pull request. Review added architecture and tests, remove unnecessary complexity, and verify that the smaller change still fixes the original problem and preserves supported behavior.
Check live ClawHub records to see how many public plugins reference a Plugin SDK method or other interface. Filter by release date, examine usage evidence and coverage gaps, and inform compatibility decisions before changing or deprecating an interface.
Build, migrate, review, and test OpenClaw interfaces with Solid 2. The skill covers state ownership, coexistence with Lit during migration, overlays such as dialogs, performance, and checks that preserve existing interface behavior.
Coordinate repairs across multiple OpenClaw issues or pull requests, which propose code changes. Assign owners, prove defects, verify fixes, and track outcomes through merging or closing resolved items within the authorized scope.
Investigate duplicate OpenClaw pull requests and issues using local history and current GitHub evidence. Organize confirmed or suspected duplicates in prtags, recording the decision, confidence, and reasons for maintainers.
Build temporary OpenClaw terminal interfaces with fixed sample data and compare two to six interactive designs side by side in tmux, a terminal pane manager, using the actual rendering components without running the full application.
Search locally archived GitHub issues and pull requests, find related discussions and possible duplicates, and check archive freshness. Verify the current GitHub state before making maintenance decisions or changing public content.
Operate the ClawSweeper maintenance bot for OpenClaw issues and pull requests, which are proposed code changes. Read findings, create repair jobs, monitor GitHub Actions, and manage automatic fixes or merges subject to authorization and validation checks.
Rebuild OpenClaw release changelogs from Git history, the recorded code changes. Group changes by user impact, preserve issue and pull request references and contributor credits, and verify the notes against the release history and published GitHub release text.
Investigate OpenClaw issues and review pull requests, proposed code changes, using current source and test evidence. Depending on the authorized scope, repair defects locally or carry the change through review, merge, and final verification.
Prepare an agent activity transcript for a GitHub pull request or issue. Extract relevant prompts, decisions, and results from local logs, remove sensitive material, and preview the edited record before separately authorized publication.
Diagnose OpenClaw problems involving models, providers, tools, and streamed responses. Use targeted logs, repeat the failing operation, and inspect stored conversations and attachments to identify the cause, guide a repair, and verify the result.
Review code using shared OpenClaw instructions and a Python helper, while also following the target repository’s review requirements. This skill points to a common installation that supplies the actual review procedure.
Route requests from OpenClaw to external coding agents such as Claude Code or Cursor. Start or continue sessions using ACP, a protocol for connecting agents, or relay prompts directly through acpx while preserving conversation context.
Launch native or web apps on a temporary Crabbox machine and display them in the chat side panel. The skill covers setup, readiness checks, screen interaction, reopening previews, and stopping apps or releasing the environment.
Turn before-and-after text or a patch into a view of changes. Create an interactive viewer URL, a PNG image, or a PDF so others can inspect edits and receive the comparison as an attachment.
Collect OpenClaw pull requests, proposed code changes, and issues shared in a specified conversation and time window. Recheck them on GitHub, assess impact and readiness, and return a prioritized queue with evidence and coverage gaps.
Manage GitHub issues and pull requests, proposed code changes, using the gh command-line tool. Create and inspect discussions, check automated test results, investigate failed logs, rerun jobs, and track authorized merges through to their verified status.
Create or revise agent skills by defining when they run, what they produce, and how their files are organized. Validate SKILL.md settings, resource links, and changed helper scripts before completing the work.
Investigate Node.js bugs by pausing execution, examining variables, and stepping through code. Diagnose stalled asynchronous work and unreliable tests, or collect memory snapshots and CPU profiles to investigate growing memory use and slow execution.
Inspect and control interactive command-line programs running in tmux, a terminal session manager. List sessions and panes, capture current output or history, send text and special keys, and watch for prompts or completion markers.
Work directly with MCP servers, which connect AI agents to external tools. List available tools, inspect their inputs, manage configuration and authentication, and call them through HTTP or local process connections using mcporter.
Test an idea before committing to full development by building a small, disposable prototype. Compare approaches under equal conditions, try a failure case, and report feasibility with commands, results, or measurements supporting the verdict.
Bundle a question and selected project files for a second AI model to review code, investigate bugs, or assess design options. Preview the files and token usage before running through an API or browser.