All categories
Code Review & Quality
Code review, refactoring, debugging, maintainability, and engineering quality
- 15,943
- 665
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse code review & quality skills
Showing 2,689–2,712 of 15,943 skills
- Reconcile Code ReviewReconcile raw specialist findings against the previous bot review and human PR comments to produce a final classified finding list.Votes: 0GitHub stars: 117
- Conventions CheckReview a pull request's title, description, and scope against the repository's PR conventions.Votes: 0GitHub stars: 117
- Code ReviewReview the changed lines of a single file in a pull request for bugs, correctness, error handling, security, and maintainability, and return structured findings.Votes: 0GitHub stars: 117
- Workers Best PracticesReviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.Votes: 0GitHub stars: 117
- Recursive SubagentUse when recursive-mode work may benefit from delegated audit, review, or bounded implementation support. This skill prioritizes phase-auditor, traceability-auditor, code-reviewer, memory-auditor, and test-reviewer roles, with mandatory self-audit fallback when subagents are unavailable.Votes: 0GitHub stars: 117
- Self ImprovementEnables agent self-reflection and learning from mistakes through systematic skill updates. Prioritizes updating existing skills over creating new ones - always searches existing skills first, creates new skills only when justified. Includes upstream source sync workflow for tracking and updating skills from databricks/databricks-agent-skills. Use after encountering errors, completing complex tasks, or when asked to reflect, learn, or document a mistake. Triggers on "learn from this", "don't r...Votes: 0GitHub stars: 6
- Ai Web Bugfix用户在 Web/UI 反馈 Bug 时，结构化收集信息并发布 PR 到 `mouxangithub/ai`（或 openpilot）。 > 详见 `ai/docs/PR_AUTOMATION.md`Votes: 0GitHub stars: 7
- Uncle BobClean Code, SOLID, and Clean Architecture principles for code review, refactoring, module design, naming, coupling/cohesion, dependency direction, and responsibility boundaries. Use when the user mentions Uncle Bob, SOLID, clean architecture, clean code, code smells, dependency inversion, single responsibility, or asks to improve code structure.Votes: 0GitHub stars: 2
- Tech Tencentcloud Industry Sre Team腾讯云行业 SRE 专家团。用于按行业场景进行腾讯云巡检、可靠性治理、架构治理、事件响应和 SLO 风险评估。来源于 WorkBuddy 技术工程卡片，并转换为 Codex 可安装的专家团入口格式。Votes: 0GitHub stars: 2
- Tech Tencentcloud Cloud Ops Team腾讯云技术支持专家团。用于 CloudQ 多云治理、AndonQ 工单与智能问答、MigraQ 迁移支持、云运维排障和架构可视化。来源于 WorkBuddy 技术工程卡片，并转换为 Codex 可安装的专家团入口格式。Votes: 0GitHub stars: 2
- Tech Tencentcloud Cloud Migration Team腾讯云上云迁移专家团。用于产品选型、Landing Zone、目标架构、迁移计划、交付实施、运维交接、FDE 部署和回滚准备。来源于 WorkBuddy 技术工程卡片，并转换为 Codex 可安装的专家团入口格式。Votes: 0GitHub stars: 2
- Tech Engineering Assurance Team工程保障团队。用于工程总监视角的代码审查、架构评审、ADR、SRE 准备、发布质量闸口和交付风险控制。来源于 WorkBuddy 技术工程卡片，并转换为 Codex 可安装的专家团入口格式。Votes: 0GitHub stars: 2
- Tech Code Review TeamEnd-to-end code review workflow. Use when the user wants a complete code review package covering GitHub PR or git diff intake, strict bug/security/performance review, project coding standards, security auditing, clean-code maintainability checks, and structured Chinese review reports. Coordinates pr-reviewer, critical-code-reviewer, project-code-standard, security-audit, clean-code-review, and code-review-assistant.Votes: 0GitHub stars: 2
- Tech Code Refactoring TeamEnd-to-end code refactoring workflow. Use when the user wants a complete refactoring package covering code structure analysis, git-history technical debt signals, Clean Code/SOLID/Clean Architecture review, refactoring pattern selection, target architecture design, behavior-preserving simplification, migration planning, and verification. Coordinates code-analyzer, agent-git-oracle, uncle-bob, code-refactoring, system-architect, and simplify.Votes: 0GitHub stars: 2
- SuperpowersSpec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan → subagent execution loop, (2) debugging a bug or test failure — triggers systematic root-cause process, (3) user says "let's build", "help me plan", "I want to add X", or "this is broken", (4) completing a feature branch — triggers test verification + merge/PR options. NOT for: one-liner fixes (just edit), reading code, or non-code tasks. Requires exec to...Votes: 0GitHub stars: 2
- SimplifyBehavior-preserving code simplification workflow for clarity, consistency, directness, and maintainability. Use when the user asks to simplify code, run /simplify, reduce unnecessary complexity, flatten conditionals, improve naming, or make recently changed code easier to read without changing behavior.Votes: 0GitHub stars: 2
- Service WidgetService Widget-style HarmonyOS service widget and meta-service card builder. Use when creating, modifying, explaining, or debugging HarmonyOS service widgets/cards, widget layouts, card resources, widget configuration, form_config.json, widget names, card abilities, static resources, logic insertion, preview/save flows, or when the user mentions Service Widget, serviceWidget, ServiceWidget, meta service, 元服务卡片, 服务卡片, 万能卡片, or CodeGenie Service Widget.Votes: 0GitHub stars: 2
- Pr ReviewerAutomated GitHub pull request review workflow with diff analysis, optional lint checks, changed-file risk assessment, security/error-handling/test-coverage findings, and structured review reports. Use when the user asks to review a GitHub PR, inspect a pull request diff, check PR risk, run local lint as part of review, or prepare PR feedback. Requires the gh CLI when fetching GitHub PRs directly.Votes: 0GitHub stars: 2
- Harness ProgressProgress Tracker HTML showing cc:WIP/cc:TODO/cc:完了 counts + drift alerts from Plans.md. Triggers: progress tracker, 進捗確認, 進捗ボード, dashboard. Skip for: implementation, review, release.Votes: 0GitHub stars: 2
- Harmony Os AskHarmonyOS Ask-style technical assistant for answering HarmonyOS/OpenHarmony, DevEco Studio, ArkTS, ArkUI, hvigor, module.json5, app.json5, main_pages.json, SDK API, lifecycle, state management, service widget, page generation, build, debugging, profiling, packaging, and publishing questions. Use when the user asks for explanation, diagnosis, guidance, best practices, API usage, or project-aware Q&A without primarily requesting code edits, or mentions HarmonyOS Ask, harmony_os_chat, 鸿蒙问答, ArkT...Votes: 0GitHub stars: 2
- Harmony Expert TeamHarmonyOS expert-team workflow for project-aware HarmonyOS/OpenHarmony work. Use when the user wants a Harmony specialist group for ArkTS, ArkUI, DevEco Studio, hvigor builds, .ets pages/components, routing, module.json5/app.json5/main_pages.json, service widgets/cards, meta services, UI generation, debugging, refactoring, Q&A, or end-to-end Harmony app delivery. Coordinates harmony-os-ask, harmony-os-act, generate-ui-code, and service-widget.Votes: 0GitHub stars: 2
- Code RefactoringCode refactoring patterns and techniques for improving code quality without changing behavior. Use when cleaning up legacy code, reducing complexity, extracting methods, removing duplication, improving maintainability, planning refactor steps, or matching code smells to safe refactoring patterns.Votes: 0GitHub stars: 2
- Code AnalyzerDeep codebase analysis workflow for architecture, execution flow, data flow, business rules, external dependencies, data models, DDD patterns, complexity, dependency maps, and technical-debt preparation. Use when the user asks to understand a codebase, generate architecture docs, identify DDD boundaries, prepare refactoring, or assess maintainability.Votes: 0GitHub stars: 2
- Clean Code ReviewClean code review and maintainability guidance for naming, small functions, responsibility boundaries, anti-patterns, code smells, KISS/DRY/YAGNI, and refactoring recommendations. Use when writing, reviewing, or refactoring code for clarity, readability, maintainability, and clean-code principles.Votes: 0GitHub stars: 2