Code-Review-Reception

Process code-review feedback by verifying items against the codebase and pushing documented updates.

149|10|Updated Oct 30, 2025
One-click install
npx skills add https://github.com/tilework-tech/nori-profiles --skill code-review-reception-tilework-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Code-Review-Reception
Source: https://github.com/tilework-tech/nori-profiles/tree/main/src/installer/features/profiles/config/_mixins/_swe/skills/receiving-code-review
Command: npx skills add https://github.com/tilework-tech/nori-profiles --skill code-review-reception-tilework-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, technically rigorous process for handling code review feedback, preventing blind implementation, ensuring clarity, and accelerating the path to a merged pull request.

Core Features & Use Cases

  • Structured Feedback Handling: Guides through fetching, understanding, clarifying, and implementing code review comments.
  • Technical Verification: Emphasizes verifying suggestions against the codebase before implementation, preventing new bugs.
  • Automated Pre-Push Checks: Integrates running tests, linting, and formatting before pushing updates.
  • Use Case: When a pull request receives multiple comments, use this skill to systematically address each one, ensuring all feedback is understood, verified, and correctly implemented before pushing new changes.

Quick Start

I've received code review feedback on my latest PR. Help me address the comments.

Frequently Asked Questions about Code-Review-Reception

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I systematically address multiple code review comments on a pull request?

Code review feedback handling involves fetching all comments, understanding each item, verifying suggestions against your codebase, implementing changes, running tests and linting, then pushing updates. This structured approach prevents blind implementation and ensures clarity before merge.

Why should I verify code review suggestions before implementing them?

Verifying feedback against your actual codebase prevents introducing new bugs or conflicts. Technical verification ensures suggestions align with your project's logic, dependencies, and existing patterns before you commit and push changes.

What checks should I run before pushing code review fixes?

Automated pre-push checks include running your test suite, linting, and formatting tools. These catches errors early and ensure your implementation meets quality standards before updating the PR.

How do I clarify unclear or ambiguous code review feedback?

When feedback is technically questionable or unclear, treat it as a multi-item workflow: fetch the comment, understand the intent, ask for clarification if needed, then verify the suggestion's validity against your codebase before implementing.

Can I use this process with my existing Git workflow?

Yes. This skill integrates within standard PR review workflows and Git-based development. It handles feedback processing, codebase verification, and pushes well-documented updates while working alongside your existing pull request practices.