skills.rest
ookamiinc
ookamiincOFFICIAL
Explore all skills by this author →
WebsiteGitHub

ookami-code-review

Enforce code review standards for pull request feedback and communication.

1|1|Updated Feb 9, 2016
Search Tags:#code review#feedback#pull request#team communication#review guidelines#comment etiquette#pr process
One-click install
npx skills add https://github.com/ookamiinc/guides --skill ookami-code-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ookami-code-review
Source: https://github.com/ookamiinc/guides/tree/main/skills/ookami-code-review
Command: npx skills add https://github.com/ookamiinc/guides --skill ookami-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clear, actionable standards for code review communication that reduce friction, align expectations, and improve PR quality across teams.

Core Features & Use Cases

  • Explicit etiquette: guidelines for respectful, constructive communication during reviews.
  • Structured feedback: expectations for comments, approvals, and requests for changes.
  • PR process alignment: applies to individual reviewers and team-based reviews, across various project styles.

Quick Start

Review a PR by applying these guidelines to craft clear, respectful and actionable feedback.

Frequently Asked Questions about ookami-code-review

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

FAQPage Schema
What are the guidelines for writing constructive code review comments?▼

Code review comments should be respectful, structured, and actionable to reduce friction. Following explicit etiquette guidelines during feedback exchanges helps align team expectations and improve overall PR quality.

How do I enforce code review standards across my team's pull requests?▼

You can enforce code review standards by applying structured feedback expectations during PR reviews. This involves setting clear guidelines for comment etiquette, approval decisions, and actionable suggestions to align team communication.

What's the best way to structure feedback during a pull request review?▼

The best way to structure pull request feedback is using clear etiquette and actionable suggestions. Structuring comments with specific expectations for approvals and requests for changes ensures traceable review history and improves team communication.

Does this code review guidance apply to individual reviewers or team-based workflows?▼

This code review guidance applies to both individual reviewers and team-based PR workflows. It supports various project styles by setting clear expectations for structured feedback, comment drafting, and PR decision making across any review process.

Can I use these review guidelines for drafting comments on any pull request?▼

Yes, you can use these review guidelines for drafting comments on any pull request. They are designed to help you craft clear, respectful, and actionable feedback during individual or team-based PR reviews and feedback exchanges.

Why do I need structured etiquette for code review communication?▼

Structured etiquette for code review communication is needed to reduce friction and align expectations across teams. Without clear standards for feedback and comment drafting, PR quality and team communication can degrade during review processes.

Related Skills

Explore More Software Engineering Skills→
Apostolos-DelisApostolos-Delis
1

create-pr

Stage, commit, push, and create a GitHub Pull Request with structured sections.

Community
Advanced
PaloAltoNetworksPaloAltoNetworks
3

ship

Automate pull request creation, CI monitoring, SonarCloud checks, and merging.

Official
Advanced
fabioc-alohafabioc-aloha
1

API Documentation Skill

Scaffold technical documentation projects with templates for API endpoints and guides.

Community
Intermediate
act70255act70255

lint-and-validate

Lint and statically analyze Node.js and Python code with ESLint, Pylint, Ruff, MyPy, and Bandit.

Community
Advanced