Process code review feedback with technical verification — not performative agreement. Fix real issues, push back on incorrect feedback with evidence.
Scanned 5/27/2026
Install via CLI
Skills Directoryopenskills install Vimalk0703/shipworthy---
name: receiving-code-review
description: Process code review feedback with technical verification — not performative agreement. Fix real issues, push back on incorrect feedback with evidence.
invoke_when: Use when processing code review feedback, addressing reviewer comments, or responding to PR review requests.
---
# Receiving Code Review
## Core Principle
**Technical verification over performative agreement.** Don't accept feedback just because it comes from a reviewer. Verify that the feedback is correct before acting on it.
## Processing Feedback
For each issue raised:
### 1. Understand the Issue
Read the feedback carefully. What exactly is the concern? Is it about correctness, style, architecture, or performance?
### 2. Verify the Claim
- If the reviewer says "this will break when X": test it. Does X actually cause a break?
- If the reviewer says "this violates architecture rule Y": check architecture.md. Does it?
- If the reviewer suggests "use pattern Z instead": is pattern Z actually better here?
### 3. Respond with Evidence
**If the feedback is correct:**
- Fix the issue
- Show the fix with test evidence
- Thank the reviewer for catching it
**If the feedback is incorrect:**
- Explain why with evidence (test results, documentation, architecture.md)
- Don't be confrontational — provide facts
- If it's a judgment call, explain your reasoning
**If the feedback is partially correct:**
- Acknowledge the valid part and fix it
- Explain why the other part doesn't apply
## Anti-Patterns
- **Performative agreement** — "Yes, you're right, I'll fix that" without verifying
- **Defensive rejection** — dismissing feedback without investigation
- **Scope creep** — using review feedback as an excuse to refactor unrelated code
- **Fix-and-forget** — fixing the symptom without understanding the root cause
## After Addressing All Feedback
1. Run the full test suite
2. Verify all Critical and Important issues are resolved
3. Summarize what was changed and why
4. Request re-review if significant changes were made
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.
Python backend development expertise for FastAPI, security patterns, database operations, Upstash integrations, and code quality. Use when: (1) Building REST APIs with FastAPI, (2) Implementing JWT/OAuth2 authentication, (3) Setting up SQLAlchemy/async databases, (4) Integrating Redis/Upstash caching, (5) Refactoring AI-generated Python code (deslopification), (6) Designing API patterns, or (7) Optimizing backend performance.
Drive the full internationalization journey for a project — detect the stack, recommend a library, set up the chosen library, wrap existing strings, and optionally connect a translation platform. Use when the user asks to add or configure i18n, internationalization, localization, multi-language support, or translations — including when they explicitly mention LinguiJS, Lingui, next-intl, "wrap strings", "find hardcoded text", "make my app translatable", or "set up translations". Triggers on g...
PTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.
