skills.rest
cipherstash
cipherstashOFFICIAL
Explore all skills by this author →
Website𝕏@cipherstashGitHub

Conducting Code Review

Review code changes and save structured feedback with severity levels.

17|Updated Oct 13, 2025
Search Tags:#automation#workflow#testing#quality assurance#code review#feedback#collaboration
One-click install
npx skills add https://github.com/cipherstash/cipherpowers --skill conducting-code-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Conducting Code Review
Source: https://github.com/cipherstash/cipherpowers/tree/main/plugin/skills/conducting-code-review
Command: npx skills add https://github.com/cipherstash/cipherpowers --skill conducting-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual code reviews are inconsistent, time-consuming, and prone to missing critical issues. This Skill standardizes the process, ensuring all checks are performed systematically, saving you time and reducing post-merge bugs.

Core Features & Use Cases

  • Systematic Review Process: Follows a structured workflow for correctness, security, and maintainability.
  • Test Verification: Mandates running all tests and checks (linting, formatting) as a non-negotiable part of the review.
  • Structured Feedback: Guides saving feedback against practice standards, including severity levels, for clear communication.
  • Use Case: Before merging a feature branch, use this Skill to ensure all code changes meet project standards, tests pass, and no critical issues are overlooked, preventing costly rework and maintaining code integrity.

Quick Start

In a Claude Code session, after making changes:

/code-review

The Skill will guide you through:

1. Identifying code scope (e.g., git log -1 --stat)

2. Running tests and checks (mise run test, mise run check)

3. Reviewing against project standards (from practices/code-review.md)

4. Saving structured feedback to your work directory

Frequently Asked Questions about Conducting Code Review

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

FAQPage Schema
How do I conduct a systematic code review before merging?▼

Code review is a structured evaluation of code changes for correctness, security, and maintainability. Start by identifying the scope of changes using git diffs, run all tests and linting checks, then provide feedback against project standards with severity levels (blocking vs. non-blocking) before merge.

What should I check when reviewing code changes?▼

Review code for correctness, security vulnerabilities, and maintainability. Verify tests pass, linting and formatting checks succeed, and changes align with project standards. Document feedback using severity levels to distinguish critical blocking issues from improvements.

Why is automating code review feedback important?▼

Manual reviews are inconsistent and time-consuming, often missing critical issues. Automating the review process with structured templates and mandatory test verification reduces post-merge bugs, ensures all checks run systematically, and prevents costly rework.

Can I use code review across different project branches and commit histories?▼

Yes, code review applies to the most recent commits and diffs across branches. It handles review requests from other agents and automated dispatches, following your project's varied practices for branch-based workflows.

What output does a code review produce?▼

Structured feedback is saved to your work directory using project conventions. The output includes identified issues with severity levels, sections validating template compliance, and clear communication of required changes before merge.

Related Skills

Explore More Software Engineering Skills→
Synaptic-Labs-AISynaptic-Labs-AI
71

pact-prepare-research

Conduct structured research and documentation gathering for the PACT Prepare phase.

Official
Advanced
MesteriisMesteriis

subagent-result-merge

Merge parallel review findings into a single actionable report.

Community
Advanced
Chai-UnChai-Un

verify

Run formatting, linting, type checks, and tests before commits.

Community
Intermediate
jimmymalhanjimmymalhan
1

evidence-proof

Execute npm test and generate confidence reports for code changes.

Community
Advanced