S Skillteca
Receber por email
Explorar Categorias Coleções Newsletter
← Voltar para o catálogo

review:self

Design e Frontend Autor: bendrucker

Self-review your own changes in a live tuicr session before committing or opening a PR. You annotate changed lines in the terminal and your comments come back to Claude as edits to apply. Replaces the difit web UI. Use for "review my changes", "self review", "let me look at the diff before committing".

15estrelas
Atualizado há 3 meses
Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add bendrucker/claude

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-self/svg)](https://www.skillteca.com.br/skills/review-self)

Skills relacionadas

Ver todas de Design e Frontend →

frontend-design

153.1k 2

Cria interfaces frontend distintas e de nível de produção com alta qualidade de design, gerando código criativo e polido e design de UI que evita a estética genérica de IA. Use para construir componentes web, páginas e aplicações, ou para estilizar/embelezar UIs web.

Design e Frontend #ai #css por anthropics

mcp-builder

153.1k

Guia para criar servidores MCP (Model Context Protocol) de alta qualidade que permitem que LLMs interajam com serviços externos por meio de ferramentas bem projetadas. Use ao construir servidores MCP para integrar APIs ou serviços externos, seja em Python (FastMCP) ou Node/TypeScript (MCP SDK).

Design e Frontend #api #llm por anthropics

webapp-testing

153.1k

Kit de ferramentas para interagir e testar aplicações web locais usando Playwright. Suporta a verificação de funcionalidades de frontend, depuração de comportamento da UI, captura de screenshots do navegador e visualização de logs do navegador.

Design e Frontend #test por anthropics

web-artifacts-builder

153.1k

Conjunto de ferramentas para criar artefatos HTML elaborados e multi-componentes para claude.ai, utilizando tecnologias web frontend modernas (React, Tailwind CSS, shadcn/ui). Use para artefatos complexos que exigem gerenciamento de estado, roteamento ou componentes shadcn/ui, não para artefatos HTML/JSX simples de arquivo único.

Design e Frontend #ai #css por anthropics

Alerta por categoria

Receba novas skills de Design e Frontend toda segunda

1 email curto, só com as skills novas de Design e Frontend. 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

Self Review

I review my own changes in tuicr; you read my comments back and apply them. The live session is the buffer: I annotate lines, you edit. Nothing lives in a hand-edited JSON file.

Load review:tuicr for session mechanics (discovery, launch, seeding, read-back, the ledger). This skill is the inbound loop on it.

Target

Default to the working tree. Override with $ARGUMENTS (staged, main..HEAD, HEAD).

Loop

  1. Launch via review:tuicr: open the target diff in a sibling tmux pane (tuicr -w for the

working tree, tuicr -r <range> for a range). Capture the session slug from tuicr review list.

  1. Self-critique (optional): offer to flag your own concerns as agent comments first

(tuicr review add --username ...), so I see your read alongside mine. Skip if I decline.

  1. Hand off: I add comments at lines (the c key) in the tuicr pane.
  2. Batch: I tell you when I am done.
  3. Live: if I ask to work as I go, arm monitor mode (review:tuicr Monitor section) and

act on each comment as it lands, holding the edits for my review.

  1. Collect: tuicr review comments --repo <repo> --session <slug>.
  2. Apply: for each comment, read the referenced file and lines, then make the edit. tuicr

reloads the diff as you go.

  1. Resolve, don't delete: tuicr exposes lifecycle_state but has no CLI to resolve a

comment, so mark each applied comment resolved with review:tuicr's ledger CLI (ledger.ts resolve <id> --action ...), keyed by the tuicr comment id. The comment stays visible. The ledger is the source of truth for open vs resolved, since the diff reload orphans rather than resolves. Sync the current comments with ledger.ts upsert first, and use ledger.ts list --open to report what remains.

  1. Repeat until I say done, then summarize what changed and what is still open (from the

ledger).

Guidelines

  • Apply comments in file order, but ask before any change that is ambiguous or that you would

push back on.

  • A comment you disagree with stays open: leave it and tell me why rather than resolving it.
  • When done, offer next steps (commit, peer review, PR) without taking them.
Compartilhar X LinkedIn