skills.rest
Hohlas
HohlasCOMMUNITY
Explore all skills by this author →
Website𝕏@Hohla2010GitHub

receiving-code-review

Restate and verify code-review feedback against the repository before implementation.

3|Updated Jun 3, 2022
Search Tags:#communication#verification#code-review#pull-request#technical-rigor#engineering-practice
One-click install
npx skills add https://github.com/Hohlas/SoSimple --skill receiving-code-review-hohlas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/Hohlas/SoSimple/tree/main/.kilocode/skills/receiving-code-review
Command: npx skills add https://github.com/Hohlas/SoSimple --skill receiving-code-review-hohlas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review feedback often contains unclear or technically questionable suggestions. This skill guides you to interpret, verify, and respond with technical accuracy before implementing changes.

Core Features & Use Cases

  • Restate the requirement from feedback to ensure alignment.
  • Verify proposed changes against the actual codebase and tests before acting.
  • Push back with technical reasoning when feedback is ambiguous or harmful.
  • Implement changes incrementally, validating each step with tests.

Quick Start

Read the feedback, restate the requirement, verify against the repository, evaluate its technical validity, and implement one item at a time with testing.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I evaluate code-review feedback before implementing changes?▼

Evaluate code-review feedback by restating the requirement, verifying proposed changes against the actual codebase, and analyzing potential impact before making incremental modifications. This process ensures technical rigor and prevents implementing ambiguous or harmful suggestions blindly.

What should I do when pull-request feedback is technically unclear or incorrect?▼

Push back on unclear pull-request feedback with technical reasoning. Restate the requirement to ensure alignment, verify the suggestion against the repository, and provide clear technical justification for your response rather than implementing questionable changes immediately.

How do I implement code-review changes incrementally with testing?▼

Implement code-review changes by addressing one item at a time, validating each modification with tests before moving to the next. This incremental approach ensures that each step maintains codebase stability and verifies the technical validity of the feedback received.

When should I push back on code-review comments?▼

Push back on code-review comments when feedback is ambiguous, technically questionable, or potentially harmful to the codebase. Restate the requirement, verify the proposed change against the repository, and use impact analysis to support your technical reasoning before responding.

What is the best way to verify code-review suggestions against a repository?▼

Verify code-review suggestions by checking them against the actual codebase and existing tests before implementation. Evaluate the technical validity of each proposed change, analyze its impact, and ensure it aligns with the original requirement before proceeding with incremental modifications.

Related Skills

Explore More Software Engineering Skills→
jokken79jokken79
1

receiving-code-review

Restate code-review feedback and verify it against the codebase before implementation.

Community
Intermediate
vp-kvp-k
12

flutter-review-receive

Evaluate Flutter code review feedback against the codebase and implement changes incrementally.

Community
Advanced
alexsandrocruzalexsandrocruz
6

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Community
Basic
leboncoinleboncoin
92

run-quality-checks

Run linting, type checking, formatting, and tests for Spark UI projects.

Official
Intermediate