📦
brainstorming
79Shape Ideas Into Implementation Designs
Early feature ideas often lack clear scope, trade-offs, and validation. This skill guides structured dialogue that turns uncertain ideas into reviewed designs.
Productivity View
Skills requesting-code-review
📦
requesting-code-review
Content revision r1 Safe ⚙️ External commands
Request Structured Code Reviews
Implementation teams need reliable review before merge. This skill guides Claude, Codex, and Claude Code through structured readiness checks.
Supports: Claude Codex Code(CC)
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "requesting-code-review" from https://skillstore.io/skills/cycleaddict-requesting-code-review.md and its manifest at https://skillstore.io/api/skills/cycleaddict-requesting-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.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "requesting-code-review". A developer asks for review after finishing a verification feature.
Expected outcome:
- Strengths: The implementation has clear separation of responsibilities and meaningful tests.
- Important issue: Progress feedback is missing for long operations.
- Assessment: Ready to continue after the important issue is fixed.
Using "requesting-code-review". A team lead requests a review before merging a new workflow.
Expected outcome:
- Strengths: The workflow follows the plan and keeps compatibility requirements visible.
- Critical issue: One failure path can skip required cleanup.
- Assessment: Not ready to merge until the cleanup path is fixed and tested.
Using "requesting-code-review". A release engineer asks for a readiness review after several tasks.
Expected outcome:
- Strengths: Tests cover the main success path and several edge cases.
- Minor issue: Documentation should mention the new review checkpoint.
- Assessment: Ready with a documentation follow-up.
Security Audit
Safev8 • 7/5/2026 Open versioned report
Static flags were false positives caused by Markdown fences, inline placeholders, and local git workflow examples. No evidence found of malicious prompt injection, data exfiltration, unsafe command construction, or system reconnaissance intent.
2
Files scanned
253
Lines analyzed
0
Review items
0
False positives ignored
Risk Factors
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.
Copy report link
https://skillstore.io/skills/cycleaddict-requesting-code-review/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/cycleaddict-requesting-code-review?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/cycleaddict-requesting-code-review?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cycleaddict-requesting-code-review/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/cycleaddict-requesting-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
Cycleaddict. (2026). requesting-code-review security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cycleaddict-requesting-code-review/audits/8BibTeX citation
@techreport{cycleaddict-cycleaddict-requesting-code-review-2026,
author = {Cycleaddict},
title = {requesting-code-review security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/cycleaddict-requesting-code-review/audits/8},
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: "requesting-code-review security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Cycleaddict"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/cycleaddict-requesting-code-review/audits/8"
identifiers:
- type: other
value: "skillstore:cycleaddict-requesting-code-review:audit:8"
description: "Skillstore immutable audit report identifier"
Compare variants
9 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
Highest Skillstore Score
Author / source Skillstore Score Evidence Confidence Skillstore usage Updated
DMJGilbert Recommended
dmjgilbert-requesting-code-review
Skillstore Score 79
Evidence Confidence High
Skillstore usage 11
Updated
2026-08-21
obra-requesting-code-review
Skillstore Score 78
Evidence Confidence High
Skillstore usage 13
Updated
2026-08-21
Cycleaddict Current
cycleaddict-requesting-code-review
Skillstore Score 78
Evidence Confidence High
Skillstore usage 12
Updated
2026-08-21
codingcossack-requesting-code-review
Skillstore Score 78
Evidence Confidence High
Skillstore usage 12
Updated
2026-08-21
sickn33-requesting-code-review
Skillstore Score 78
Evidence Confidence High
Skillstore usage 11
Updated
2026-08-21
cygnusfear-requesting-code-review
Skillstore Score 78
Evidence Confidence High
Skillstore usage 7
Updated
2026-08-21
davila7-requesting-code-review
Skillstore Score 78
Evidence Confidence High
Skillstore usage 4
Updated
2026-08-21
dyai2025-requesting-code-review
Skillstore Score 75
Evidence Confidence Medium
Skillstore usage 8
Updated
2026-08-21
zhanlincui-requesting-code-review
Skillstore Score 70
Evidence Confidence High
Skillstore usage 440
Updated
2026-08-21
Skillstore Score
Why this score Evidence Confidence: High 55
Architecture
85
Maintainability
87
Content
71
Community
83
Spec Compliance
What You Can Build
Review a Completed Task
Check a finished development task before starting the next task in a plan.
Validate a Feature Before Merge
Compare a major feature against requirements and identify blocking issues before merge.
Strengthen Release Readiness
Use a consistent review checklist to assess bugs, tests, documentation, and compatibility.
Try These Prompts
Review My Latest Task
Review my latest completed task before I continue. Compare it with the requirement and give a clear readiness verdict.
Check Feature Completion
Review this feature against the plan. Categorize issues by severity and note what must change before merge.
Run a Pre-Merge Review
Review the selected git range for production readiness. Focus on correctness, tests, architecture, security, and breaking changes.
Audit Multi-Step Work
Review the completed batch of tasks against the implementation plan. Identify compounded risks and decide whether work should continue.
Best Practices
- Request review after each meaningful task, not only at the end of a project.
- Provide accurate requirements and git revisions so the reviewer can compare intent with implementation.
- Fix critical and important issues before continuing to later work.
Avoid
- Do not ask for a vague review without requirements or a revision range.
- Do not treat a positive assessment as a substitute for running tests.
- Do not dismiss important feedback without technical evidence.
Frequently Asked Questions
What does this skill help review?
It helps review completed code changes against requirements, tests, architecture, and production readiness.
Does it run the code automatically?
No. It provides a review workflow and template that an AI agent can use with repository context.
Why does it ask for base and head revisions?
The revisions define the exact change range so the reviewer can focus on relevant work.
Can it replace human code review?
No. It supports human reviewers by finding issues early and organizing feedback clearly.
Which tools can use this skill?
The report lists support for Claude, Codex, and Claude Code.
How should teams handle reviewer feedback?
Fix critical and important issues first, record minor issues, and challenge incorrect feedback with evidence.
Developer Details
Author
CycleaddictLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Repository
https://github.com/Cycleaddict/generic-superpowers/tree/main/skills/requesting-code-reviewRef
02f077c174c5335e2f5d02ca15e77b70d9543e58
Maintenance freshness
7/18/2026
Usage
8 downloads · 261 views
File structure
More from Cycleaddict
View all📦
dispatching-parallel-agents
79Dispatch Parallel Coding Agents
Sequential debugging slows teams when failures are independent. This skill shows how to split focused tasks across parallel AI agents and integrate results safely.
Coding & Development View
📦
writing-plans
78Create Detailed Coding Plans
Complex implementation work can fail when tasks, files, tests, and handoffs are unclear. This skill helps Claude, Codex, and Claude Code create detailed plans with small steps, exact paths, tests, and execution options.
Coding & Development View
📦
executing-plans
78Execute Implementation Plans with Checkpoints
Long implementation plans are easy to rush or execute without review. This skill guides Claude, Codex, and Claude Code through batched work with verification checkpoints.
Coding & Development View
📦
test-driven-development
78Write Better Code with Test-First Development
Feature work and bug fixes can ship with weak tests when testing comes after implementation. This skill guides Claude, Codex, and Claude Code through strict test-first cycles, failure verification, minimal implementation, and refactoring.
Coding & Development View
📦
receiving-code-review
78Evaluate Code Review Feedback
Code review feedback can be unclear, incomplete, or technically wrong for the current codebase. This skill gives Claude, Codex, and Claude Code a verification workflow before changing code.
Coding & Development View
Related Skills
View all📦
workflow-patterns
80Implement Tasks with TDD Workflow
by sickn33
Task plans can drift when implementation, tests, commits, and approvals are handled inconsistently. This skill provides a structured TDD workflow with checkpoints, verification gates, and git tracking.
Coding & Development View
📦
git-advanced
86Master Advanced Git Workflows
by AutumnsGrove
Complex Git maintenance can make history changes and conflict resolution difficult. This skill provides structured guidance, recovery steps, and an optional local helper for common advanced workflows.
Coding & Development View
📦
code-reviewer
83Review Code with Structured Quality Checks
by alirezarezvani
Code reviews can miss quality, security, and maintainability issues. This skill guides structured reviews with scripts, checklists, and report generation.
Coding & Development View
📦
senior-qa
81Improve QA Coverage for Web Apps
by alirezarezvani
Modern teams need clear test strategy and practical automation without slowing delivery. This skill helps Claude, Codex, and Claude Code plan tests, review coverage, and scaffold QA workflows.
Coding & Development View
📦
coding-agent-pm
81Manage Coding Agent Workflows
by kiwi-phantomworks
Coding-agent projects can drift when tasks, scope, and checks are vague. This skill gives PM templates and review rules that keep Claude, Codex, and Claude Code work bounded and verifiable.
Coding & Development View
📦
code-review
80Review Code for Bugs and Security Issues
by 21pounder
Code reviews can miss bugs, security flaws, and maintainability issues. This skill guides Claude, Codex, and Claude Code through structured review steps.
Coding & Development View