>

Comprehensive Git workflow automation including branching strategies, pull request creation, code reviews, merge strategies, and release management. Use when Claude needs to help with Git operations, branching models (Git Flow, GitHub Flow), pull request creation, code reviews, merge conflicts, or release processes.

>-

Run the AI Voice Analyzer on blog content to detect AI-sounding patterns and get actionable rewrite suggestions. Use when reviewing or improving blog articles before publishing.

This skill should be used when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes. It provides ADR templates and best practices.

Track and evaluate AI predictions over time to assess accuracy. Use when reviewing past predictions to determine if they came true, failed, or remain uncertain.

Runs a strict-but-fair ICLR/CVPR/SIGGRAPH reviewer challenge on idea, roadmap, or full paper, with major-risk diagnostics and actionable repair paths. Use when the user wants high-pressure review questioning instead of brainstorming.

Reviews GitHub pull requests for the Medusa repository. Checks PR template compliance, contribution guidelines, code conventions, and community contribution limits. Posts a review comment and applies initial-approval or requires-more label. Use when a PR is opened or updated.

Analyze a GitHub pull request including diff, comments, related issues, and local code context

Comprehensive pull request review using specialized agents

Use for QUICK PR reviews with structured checklists (architecture, patterns, security, performance). Provides step-by-step review process, git diff commands, and review report templates. Best for pull request reviews and pre-commit checks. NOT for deep refactoring analysis (use code-review instead).

'PR creation workflow, title format, description template, and quality gates'

Start the multi-AI pipeline with a given request. Guides through plan -> review -> implement -> review workflow.

React 19 and Next.js 16 performance optimization for the Arcanea platform. Use when writing, reviewing, or refactoring React components, data fetching logic, bundle optimization, or any frontend performance work. Triggers on: React components, Next.js pages, hooks, data fetching, bundle size, re-renders, Server Components, Client Components, hydration. Sourced from Vercel Engineering's official React best practices (57 rules, 8 categories) and adapted for the Arcanea stack.

Use when scanning code, skills, dependencies, or configurations for security vulnerabilities, threat modeling, secrets exposure, insecure defaults, auth issues, and hardening opportunities.

Audit SoulMap AI evals so datasets, assertions, source markers, and golden responses stay source-backed, failure-oriented, and hard to game.

Start work on a new PR — review context and propose a mid-level approach

Reference for agents working with the workflow checkpoint system.

Review an entity store PR

Mandatory core-4 reviewer with P0-P3 severity classification and specialist escalation

Create a GitHub pull request from current working changes. Handles all git states - uncommitted changes, no branch, unpushed commits, etc. Analyzes diffs and changesets to generate a PR with filled-in template. Opens the PR in the browser when done. Use when the user asks to create a PR, open a PR, submit changes, or push for review.

Authoring and styling guidelines for the Opentrons /docs MkDocs project. Covers file conventions, frontmatter, page titles, header IDs, image formats, tables, code blocks, Python API reference (mkdocstrings, autorefs, macros), and CSS patterns (parts lists, screenshots, icons, instruction lists, side-by-side figures, fonts, colors). Use when writing, editing, or reviewing any file in the docs/ directory, or when the user asks about MkDocs conventions, docstrings, CSS classes, or the Python API reference.

Fix a pull request based on review feedback

Collection of project-specific skills for Contentstack CLI monorepo development. Use when working with CLI commands, testing, framework utilities, or reviewing code changes.

Create or update GitHub pull requests using gh CLI. Use when creating PRs, updating PR titles/descriptions, opening pull requests, or submitting changes for review.

Create, review, and merge GitHub pull requests using GitHub CLI and best practices. Use when the user asks to open a PR, review a PR, merge a branch, squash merge, or work with GitHub pull requests and merges.

Prepare code for review by running quality checks, creating conventional commits, and opening pull requests. Use when the user wants to commit changes, create a PR, prepare for code review, or asks to commit their work.

Applies project Git commit message conventions. Use when writing commit messages, reviewing staged changes, or when the user asks for git commit help.

>

Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.

Practical guide for creating human-readable and agent-parseable diagrams using Mermaid. Includes conservative, renderer-compatible templates and when-to-use guidance.

Uses the Selora AI MCP server to inspect home state, validate/create automations, manage automation lifecycle, and handle proactive pattern/suggestion workflows. Use when users ask to analyze their home, review Selora automations, validate YAML, create/enable/delete automations, list or act on suggestions/patterns, trigger a scan, or continue Selora chat sessions.

METAINFORMANT rules for directory scripts. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, no mocks.

Generate a sprint review changelog from GitHub pull requests. Lists PRs by a given author since a given date, groups them into Features and Fixes, and writes a markdown summary.

以资深架构师视角对 Diff/源码做深度 Code Review：正确性与防御性、架构合规、DRY、KISS、测试完备性；禁止格式挑刺；单次最多 5 条高价值问题；无重大问题输出 LGTM。在用户附上改动、请求审查、PR review、走查、diff 评审时触发。

Generate or review least-privilege MCP configs for this project.

Describes the sub-agent pipeline: task-decomposer breaks a task into subtasks, task-worker implements them, work-reviewer checks the result; on issues feedback goes back to the worker. Use when orchestrating multi-step work with task-decomposer, task-worker, and work-reviewer agents, or when the user asks how these agents work together.

Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.

Enforces Next.js 16 best practices for App Router, React Server Components, caching, routing, TypeScript, and performance. Use when building, reviewing, or refactoring Next.js applications, creating pages/layouts/routes, configuring next.config.ts, handling data fetching, or working with server/client components.

Serve MarkdownViewer-web-pro locally for testing. Use when the user says /localdeploy, asks to test locally, run a local server, or preview before pushing.

Translates discovery and product design artifacts into implementation-ready backend specifications. Produces API contracts (OpenAPI), schema design, auth model, and integration point specs for human r

Goal: build a skill that finds real vulnerabilities while minimizing false positives.

Verify an E2E test fix by running the test multiple times and checking code quality

Process all unaddressed PR review comments in parallel. Each comment gets a dedicated subagent that either applies the fix or replies with technical reasoning for disagreement.

Guides writing clear, well-structured technical documentation following Mintlify's best practices (Diátaxis framework, audience awareness, style/tone, navigation, SEO/AEO). Use when writing, reviewing, or improving documentation, guides, tutorials, API references, or any user-facing technical content.

>-

Reviews local git changes and generates a pull request summary following the project template. Use when the user asks to automate PR summary, generate PR description, fill PR template, or review local changes for a PR.

Add or modify tasks in Implementation Plan. Use when user proposes new requirements, changes priorities, or adjusts existing task scope.

'Stage files and create a conventional commit with a well-formed message.'