Habilidades receiving-code-review
🔍

receiving-code-review

Seguro 🌐 Acesso à rede⚙️ Comandos externos

Evaluate code review feedback with technical rigor

Também disponível em: obra,DYAI2025,Cycleaddict,davila7,CodingCossack

Code review feedback often requires verification before implementation. This skill ensures Claude evaluates suggestions technically, asks clarifying questions when needed, and pushes back when feedback is incorrect or unclear.

Suporta: Claude Codex Code(CC)
📊 70 Adequado
1

Baixar o ZIP da skill

2

Upload no Claude

Vá em Configurações → Capacidades → Skills → Upload skill

3

Ative e comece a usar

Testar

A utilizar "receiving-code-review". Reviewer suggests removing legacy code and adding proper metrics tracking with database, date filters, and CSV export

Resultado esperado:

  • Suggestion requires YAGNI check - grep codebase for actual usage
  • Current implementation: endpoint exists but is unused
  • Recommended response: 'This endpoint has no callers. Remove it (YAGNI)? Or is there usage I'm missing?'
  • Do not implement database metrics until actual use cases are identified

A utilizar "receiving-code-review". Code review feedback says: Fix items 1-6, but I only understand 1, 2, 3, and 6. Items 4 and 5 are unclear.

Resultado esperado:

  • Do NOT implement items 1, 2, 3, 6 yet - unclear items may be related
  • Request clarification on items 4 and 5 before proceeding
  • Recommended response: 'I understand items 1, 2, 3, 6. Need clarification on 4 and 5 before implementing.'

Auditoria de Segurança

Seguro
v5 • 1/16/2026

This skill contains only markdown documentation with behavioral guidelines for code review response patterns. No executable code, no file system access, no network calls, no command execution. All 33 static findings are FALSE POSITIVES caused by the scanner misidentifying markdown syntax and plain text as security-relevant patterns.

2
Arquivos analisados
384
Linhas analisadas
2
achados
5
Total de auditorias
Auditado por: claude Ver Histórico de Auditoria →

Pontuação de qualidade

38
Arquitetura
100
Manutenibilidade
87
Conteúdo
22
Comunidade
100
Segurança
91
Conformidade com especificações

O Que Você Pode Construir

Verify review suggestions

Evaluate external code review feedback before implementation to prevent introducing bugs or regressions

Maintain code quality

Ensure code review feedback is technically sound and appropriate for the specific codebase context

Improve code review process

Establish consistent standards for evaluating and responding to code review feedback

Tente Estes Prompts

Evaluate suggestion
Use the receiving-code-review skill to evaluate this suggestion: [paste feedback]. Check if it is technically correct, breaks existing functionality, or conflicts with project decisions.
Request clarification
I received code review feedback but do not fully understand some items. Use receiving-code-review to help me identify what needs clarification and how to ask effectively.
Push back correctly
I believe a code review suggestion is technically incorrect. Use receiving-code-review to help me construct a technical, evidence-based pushback response.
Verify before implementing
I want to implement code review feedback but need to verify it first. Use receiving-code-review to guide me through the verification checklist.

Melhores Práticas

  • Always verify code review feedback against the actual codebase before implementation
  • Ask clarifying questions when any item is unclear rather than guessing
  • Use technical reasoning when pushing back, not defensiveness or apologies

Evitar

  • Performative agreement like 'You're absolutely right!' or 'Great point!'
  • Blind implementation of suggestions without technical verification
  • Batch implementing multiple items without testing each one individually

Perguntas Frequentes

What AI tools support this skill?
Works with Claude, Codex, and Claude Code for evaluating code review feedback.
Does this skill execute code changes?
No. This skill provides behavioral guidelines for evaluation only. It does not modify code.
How is this different from normal Claude behavior?
Adds systematic verification steps, clarifies when to push back, and avoids performative agreement.
What data does this skill access?
No data access. It is a prompt-based skill providing response guidelines only.
What if feedback seems correct but I cannot verify it?
State the limitation: 'I cannot verify this without [X]. Should I investigate, ask, or proceed?'
How does this compare to a linter or code analyzer?
This skill guides behavioral response to human feedback, not automated code analysis or error checking.

Detalhes do Desenvolvedor

Estrutura de arquivos

📄 SKILL.md