Skills receiving-code-review
📦

receiving-code-review

Content revision r1 Safe ⚙️ External commands

Handle Code Review Feedback

Code review feedback can be unclear, incomplete, or technically wrong. This skill helps Claude, Codex, and Claude Code verify feedback before changing code.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

This skill is part of a pack

Install the whole pack to get every skill the task needs, in one command.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "receiving-code-review" from https://skillstore.io/skills/zhanlincui-receiving-code-review.md and its manifest at https://skillstore.io/api/skills/zhanlincui-receiving-code-review/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Test it

Using "receiving-code-review". Reviewer asks to remove legacy code, but old platform support may still be required.

Expected outcome:

The response should verify platform targets first, then propose keeping or removing the legacy path based on evidence.

Using "receiving-code-review". A reviewer sends six items, and two are unclear.

Expected outcome:

The response should summarize understood items and ask for clarification on the unclear ones before implementation.

Using "receiving-code-review". A reviewer asks for a larger feature that may not be used.

Expected outcome:

The response should check actual usage and ask whether to remove unused scope instead of expanding it.

Security Audit

Safe
v4 • 7/8/2026 Open versioned report

No executable Ruby or shell backtick use was found in the skill. The external command alerts point to Markdown code fences and prose examples, and the network reconnaissance alert points to ordinary guidance text.

1
Files scanned
214
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/zhanlincui-receiving-code-review/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/zhanlincui-receiving-code-review/security.svg)](https://skillstore.io/skills/zhanlincui-receiving-code-review?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/zhanlincui-receiving-code-review?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/zhanlincui-receiving-code-review/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/zhanlincui-receiving-code-review.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

ZhanlinCui. (2026). receiving-code-review security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zhanlincui-receiving-code-review/audits/4

BibTeX citation

@techreport{zhanlincui-zhanlincui-receiving-code-review-2026, author = {ZhanlinCui}, title = {receiving-code-review security audit report (audit version 4)}, institution = {Skillstore}, year = {2026}, number = {4}, url = {https://skillstore.io/skills/zhanlincui-receiving-code-review/audits/4}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "receiving-code-review security audit report (audit version 4)" version: "unspecified" type: report authors: - name: "ZhanlinCui" date-released: "2026-07-08" url: "https://skillstore.io/skills/zhanlincui-receiving-code-review/audits/4" identifiers: - type: other value: "skillstore:zhanlincui-receiving-code-review:audit:4" description: "Skillstore immutable audit report identifier"

Compare variants

8 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Higher Skillstore usage
sickn33 Recommended

sickn33-receiving-code-review

Skillstore Score 79
Evidence Confidence High
Skillstore usage 14
Updated

2026-08-21

codingcossack-receiving-code-review

Skillstore Score 79
Evidence Confidence High
Skillstore usage 6
Updated

2026-08-21

ZhanlinCui Current

zhanlincui-receiving-code-review

Skillstore Score 78
Evidence Confidence High
Skillstore usage 43
Updated

2026-08-21

obra-receiving-code-review

Skillstore Score 78
Evidence Confidence High
Skillstore usage 25
Updated

2026-08-21

cycleaddict-receiving-code-review

Skillstore Score 78
Evidence Confidence High
Skillstore usage 8
Updated

2026-08-21

davila7-receiving-code-review

Skillstore Score 78
Evidence Confidence High
Skillstore usage 7
Updated

2026-08-21

cygnusfear-receiving-code-review

Skillstore Score 78
Evidence Confidence High
Skillstore usage 7
Updated

2026-08-21

dyai2025-receiving-code-review

Skillstore Score 75
Evidence Confidence Medium
Skillstore usage 9
Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
85
Content
70
Community
91
Spec Compliance

What You Can Build

Review Triage

Separate clear review items from unclear or risky requests before implementation.

Technical Pushback

Prepare concise evidence when a review suggestion conflicts with codebase requirements.

Pull Request Follow-Up

Respond to inline comments with factual updates after each verified change.

Try These Prompts

Check Feedback
Review this feedback and restate each requested change. Mark any item that needs clarification before implementation.
Verify Suggestion
Evaluate this review suggestion against the current codebase. Explain whether it is correct, risky, or unclear.
Plan Review Fixes
Create an implementation order for these review comments. Prioritize blocking issues, simple fixes, and complex refactors.
Draft Evidence-Based Reply
Draft a concise review reply that explains the technical evidence, states the tradeoff, and asks for direction if needed.

Best Practices

  • Read all feedback before changing code.
  • Verify each suggestion against tests, usage, and platform constraints.
  • Handle one reviewed change at a time and test each result.

Avoid

  • Do not accept review feedback before checking the codebase.
  • Do not implement unclear items while leaving related items unresolved.
  • Do not add broad features when the reviewed code is unused.

Frequently Asked Questions

Does this skill implement review feedback automatically?
No. It guides how to evaluate feedback before implementation.
Can it help when a reviewer is wrong?
Yes. It encourages evidence-based pushback when the suggestion conflicts with codebase facts.
Does it require GitHub?
No. The guidance applies to any code review process, including GitHub review threads.
Can it help with unclear review comments?
Yes. It tells the assistant to ask for clarification before making related changes.
Is this useful for Claude Code and Codex?
Yes. It is designed for Claude, Codex, and Claude Code workflows.
Does it replace reviewer judgment?
No. It helps structure verification, questions, and implementation decisions.

Developer Details

Author

ZhanlinCui

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Ref

88a205c7f635a966e31156313b590d59007c5caa

Maintenance freshness

7/18/2026

Usage

42 downloads · 181 views

File structure

📄 SKILL.md