Loading...
Loading...
Found 1,264 Skills
Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", or "readable code". Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.
Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.
Use when reviewing a plan before implementation begins. Not for autonomous plan analysis — use plan-review agent instead. Challenges scope, walks through architecture/quality/tests/performance interactively with mandatory user checkpoints and opinionated recommendations.
Use when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage. Examples: "Review this PR", "What does PR #42 change?", "Is this PR safe to merge?"
Use Codex CLI for sandboxed auditing, debugging, and autonomous prototyping
Defense-in-depth verification before declaring any task complete. Run tests, check build, validate changed files, verify no regressions. Applies 4-level adversarial artifact verification (EXISTS > SUBSTANTIVE > WIRED > DATA FLOWS) with goal-backward framing. Use before saying "done", "fixed", or "complete" on any code change. Use for "verify", "make sure it works", "check before committing", or "validate changes". Do NOT use for debugging (use systematic-debugging) or code review (use systematic-code-review).
Assist developers in writing clean, maintainable code following software engineering best practices. Use when conducting code reviews, refactoring code, enforcing coding standards, seeking guidance on clean code principles, or integrating automated quality checks into development workflows.
Analyze what code will be affected by changes. Use when user asks "what will break if I change X", "impact of changing X", "dependencies of X", "is it safe to modify X", or before making significant code changes.
Run Claude Code review against the current branch, fix only the review comments that are still valid for the current codebase, and leave invalid comments unchanged.
Reviews DataHub connector implementations against 22 golden standards for compliance, code quality, silent failures, test coverage, type design, and merge readiness. Use when reviewing connector code, checking a PR, auditing a connector implementation, or verifying connector standards compliance.
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
Python code refactoring skills, covering code smell identification, design pattern application, readability improvement, and practical experience. This skill is applicable when users request "refactor code", "refactor", "code optimization", "improve code quality", "code smell review", "apply design patterns", "enhance readability", or submit code review requests. It supports generating structured refactoring documents after refactoring completion ("output refactoring document", "generate refactoring report"). It includes practical patterns extracted from 20+ real refactoring PRs in the vllm-ascend repository.