Skills matching the name, description or GitHub author.
Create and manage workflows that guide the Agent through repetitive tasks. Use this skill when users want to create new workflows, update existing workflows, or need guidance on writing effective step-by-step w...
This skill should be used when the user asks to "finalize", "/finalize", "ship it", "ship this", "wrap up", "wrap this up", or "finish and commit". Orchestrates the complete workflow for finishing development w...
This skill should be used when the user asks to "review code", "code review", "check my changes", "review this PR", "review my implementation", "PR review", "look at my code", or when reviewing GUI automation c...
Comprehensive code review with failure scenario analysis, security checks, and prioritized fix suggestions. Use after /execute to validate implementation quality.
This skill provides guidance on using OpenAI's Codex CLI for detail-oriented code analysis. Use when the user explicitly invokes "/codex", asks to "use codex", "run codex", "have codex review", or when Claude d...
Expert-level frontend code review workflow focusing on maintainability, security, performance, and accessibility. Use when reviewing frontend diffs, PRs, components, SPAs, UI logic, or framework-specific code (...
Orchestrate multi-agent development workflows. Use when starting a new feature to coordinate architecture design, implementation, code review, and release through specialized sub-agents.
Code Reviewer persona definition
Security audit for code review and vulnerability analysis
Security audit guidelines covering OWASP Top 10 vulnerabilities, secure coding practices, authentication patterns, and code review checklists
Activates when user requests architecture analysis, code review, refactoring suggestions, design pattern evaluation, or SOLID principles assessment. Do NOT use for security-specific audits (use security-auditor...
Code review for all uncommitted changes (staging status is irrelevant). Checks CLAUDE.md compliance, identifies bugs, security issues, style problems, and simplification opportunities.
Apply a production-grade code review checklist for Java backend changes: layering, error handling, security, tests, observability, performance, and maintainability. Use when preparing a PR or reviewing one.
This skill should be used when writing code in any opinionated framework's distinctive style. It applies when writing framework-based applications, creating models/controllers/views, or any framework code. Trig...
This skill teaches proper Gemini CLI usage patterns. Use stdin piping instead of shell variable gymnastics. Covers code review, plan review, and general prompts.
Universal code review checklist and guidelines. Use when reviewing PRs, checking code quality, or providing feedback on code changes.
Prepare structured PR reviews using a three-phase framework (Context, Analysis, Validation). Use when reviewing pull requests, when user shares a PR URL, or mentions "review PR", "code review", or "check this P...
Create a Linear issue. Use when user asks to create an issue, register a task, track work, or needs a ticket before starting development. Do NOT load for: implementation work, code review, deployment.
Start work on a Feature/Bug/Chore issue by creating a git worktree. Use when user wants to work on something, implement a feature, start development, or confirms work on a Linear issue. Uses Linear's auto-gener...
Code review against C# 14 standards. Four modes: standards, performance, architecture, full. Use for "/review", "check code", "performance review".
Perform a comprehensive code review
Code review focused on readability, maintainability, and clarity. Use after code changes, before merging, or when reviewing pull requests.
Review code changes for correctness, security, tests, and architecture; use for code review or PR review requests (trigger keywords: code review, review changes, PR review, security review).
Conduct comprehensive code reviews using software engineering best practices, clean code principles (SOLID, DRY, KISS, YAGNI), security checks, and performance analysis. Use when reviewing code changes, pull re...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.