code-polishPre-release code review - runs lint/type checks, then launches 3 parallel review agents (cleanliness, design, efficiency) to analyze the diff, synthesizes a...
Install via ClawdBot CLI:
clawdbot install tenequm/code-polishGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://www.apache.org/licenses/Audited Apr 17, 2026 · audit v1.0
Generated May 5, 2026
A developer runs 'review code' before committing to ensure all changes pass linting, type checks, and a thorough multi-agent review. This catches debug leftovers, design issues, and inefficiencies early.
Before pushing a release branch, the team triggers 'polish before release' to get a unified report on cleanliness, design, and efficiency. The skill fixes any issues automatically with approval.
Integrated into a CI pipeline, the skill runs on every pull request to provide a structured diff analysis. It highlights reuse opportunities and potential performance regressions for human reviewers.
New team members use 'review changes' on unfamiliar code to get explanations of diffs and suggestions for improvement, accelerating their understanding of project conventions and existing utilities.
During large refactors, the skill flags copy-paste variations, parameter sprawl, and redundant state. It helps ensure refactored code aligns with design patterns and doesn't introduce new issues.
Offer basic reviews (lint/type check only) for free, with advanced multi-agent analysis and auto-fix as a premium feature. Revenue from subscriptions.
License the skill to organizations for use across multiple repositories and teams. Includes dedicated support, custom rule sets, and integration with internal CI/CD.
Sell the skill on AI agent marketplaces (e.g., Claude, OpenAI) as a premium add-on. Developers purchase once and use it indefinitely.
💬 Integration Tip
Configure the skill's trigger phrases in agent settings and ensure CLAUDE.md specifies the correct lint/type-check command for your project.
Scored May 5, 2026
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Use the @steipete/oracle CLI to bundle a prompt plus the right files and get a second-model review (API or browser) for debugging, refactors, design checks, or cross-validation.
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Systematic code review patterns covering security, performance, maintainability, correctness, and testing — with severity levels, structured feedback guidance, review process, and anti-patterns to avoid. Use when reviewing PRs, establishing review standards, or improving review quality.
Coding style memory that adapts to your preferences, conventions, and patterns for consistent coding.
Provides a 7-step debugging protocol plus language-specific commands to systematically identify, verify, and fix software bugs across multiple environments.