review-gate

Name: review-gate
Author: cukas

Automação

Autor: cukas

Use after completing any code implementation, bug fix, or refactor. Structured review with pass/fail verification before declaring done.

0estrelas

Atualizado há 7 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add cukas/claude-workflow-skills

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/review-gate-cukas/svg)](https://www.skillteca.com.br/skills/review-gate-cukas)

#ai

Skills relacionadas

Ver todas de Automação →

MoneyPrinterTurbo

90.3k

利用AI大模型，一键生成高清短视频 Generate short videos with one click using AI LLM.

Automação por harry0703

weather-svg-creator

58.4k

Creates an SVG weather card showing the current temperature for Dubai. Writes the SVG to orchestration-workflow/weather.svg and updates orchestration-workflow/output.md.

Automação #ai por shanraisshan

asana-automation

41.2k

Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.

Automação #git #github por sickn33

payment-integration

41.2k

Integrate Stripe, PayPal, and payment processors. Handles checkout flows, subscriptions, webhooks, and PCI compliance. Use PROACTIVELY when implementing payments, billing, or subscription features.

Automação #git #github por sickn33

Alerta por categoria

Receba novas skills de Automação toda segunda

1 email curto, só com as skills novas de Automação. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Review-Gate

Structured post-implementation review. Nothing passes without evidence.

1. Trace affected code paths

Use Read, Grep, and Glob to trace the call chain from each changed function to its callers and dependents. For changes that touch multiple files or cross API boundaries, trace both directions.

2. Bug pattern scan

Check every changed file for:

Null safety: optional chaining gaps, unchecked nullable values, NonNullable casts without guards
Async errors: missing

[Description truncada. Veja o README completo no GitHub.]

Compartilhar X LinkedIn