Loading...
Loading...
Found 1,267 Skills
Submit commits as Phabricator diffs for code review using Sapling.
Guides writing, reviewing, and reasoning about modern Android UI code using Jetpack Compose. Covers best practices for state management, side effects, recomposition, navigation, Material 3 design, accessibility, and performance. Use when reading, writing, or reviewing any Jetpack Compose project.
This is used to review comments on an active pull request and decide whether to accept, iterate, or reject the changes suggested in each comment.
Expert code reviewer for TypeScript + React 19 applications. Use when reviewing React code, identifying anti-patterns, evaluating state management, or assessing code maintainability. Triggers: code review requests, PR reviews, React architecture evaluation, identifying code smells, TypeScript type safety checks, useEffect abuse detection, state management review.
GPU Code to Ascend NPU Adaptation Review Expert. When users need to migrate GPU-based code (especially deep learning and model inference-related code) to Huawei Ascend NPU, this skill must be used for comprehensive review. This skill can identify bottlenecks in GPU-to-NPU migration, write adaptation scripts, generate verification plans, and output a complete Markdown review report. Trigger scenarios include: users mentioning keywords such as "NPU adaptation", "Ascend migration", "GPU to NPU", "Ascend", "CANN", "model migration", "operator adaptation", or users requesting to review GPU code repositories and migrate to the NPU platform.
Comprehensive Elixir/Phoenix code review with optional parallel agents
Umbrella skill for agent work discipline across development, analysis, and documentation: inspect the repo before restructuring, keep durable truth in repo artifacts instead of chat memory, co-evolve specs/design/steering/user docs with code, apply sound coding patterns, verify work honestly, avoid shortcuts, work efficiently with subagents without hallucinating, and keep moving through the next concrete work item when the human is away. References cover coding patterns, AI-authored code review, and artifact co-evolution. Trigger when the user asks for workflow discipline, coding patterns, doc/artifact maintenance, code review of AI-authored code, project hygiene, execution guardrails, repo normalization, or when a task risks drifting across architecture, storage, specs, continuity, or tooling boundaries.
Use when a GitHub Pull Request needs review-thread reply and resolve handling, findings ingestion, and a mandatory final gate in one PR-scoped session.
Small tweaks to existing features — no design needed, just TDD and PR
Launch an isolated Claude reviewer for the current branch, a specific commit, or uncommitted changes. Uses Claude's agent runtime with worktree isolation so the review has an independent read-only view of the code before findings are reported back.
Scans code for security vulnerabilities — injection flaws, authentication gaps, XSS vectors, mass assignment, CSRF, insecure deserialization, sensitive data exposure, broken access control, and misconfigurations. Generates severity-scored findings with copy-pasteable fix prompts. Trigger phrases: "security scan", "security audit", "vulnerability check", "find security issues".
Review changed code for reuse, quality, and efficiency, then fix any issues found.