skills.rest
nseluga
nselugaCOMMUNITY
Explore all skills by this author →
GitHub

review

Review code changes against coding standards and issue tracker requirements.

Updated Jul 2, 2026
Search Tags:#code quality#code review#parallel sub-agents#two-axis review#issue tracker integration
One-click install
npx skills add https://github.com/nseluga/os --skill review-nseluga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/nseluga/os/tree/main/skills/review
Command: npx skills add https://github.com/nseluga/os --skill review-nseluga

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a thorough review of code changes against two critical axes: adherence to coding standards and fulfillment of the specified requirements.

Core Features & Use Cases

  • Two-axis Review: Simultaneously checks code against coding standards and the originating issue/PRD.
  • Parallel Sub-agents: Ensures that the reviews do not interfere with each other's context.
  • Integration with Issue Tracker: Requires an issue tracker for referencing originating specifications.
  • Use Case: Ideal for reviewing branches, pull requests, or work-in-progress changes to ensure both compliance and correctness.

Quick Start

Run the review skill with the command: /review <commit-hash> to review changes since the specified commit.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review code changes against both coding standards and PRD requirements?▼

Conduct a two-axis code review by running the skill against a commit hash, which triggers parallel sub-agents to evaluate changes against coding standards and originating issue specifications independently.

What is a two-axis code review and how does it work?▼

A two-axis code review evaluates changes simultaneously for adherence to coding standards and fulfillment of specified requirements, using parallel sub-agents to ensure independent reviews do not interfere with each other's context.

Do I need a local issue tracker to review pull requests?▼

Yes, a local issue tracker is required to reference originating specifications and provide spec context during the code review process.

Can I review work-in-progress git branches without a full pull request?▼

Yes, you can review work-in-progress changes by running the skill with a target commit hash, which uses git diffing to isolate and review the specific code changes.

What's the best way to ensure parallel code reviews do not interfere with each other?▼

Using parallel sub-agents for independent reviews ensures that context does not interfere, allowing simultaneous evaluation of coding standards and requirement fulfillment without cross-contamination.

Does the code review skill require git for diffing changes?▼

Yes, git is required for diffing code changes, allowing the review process to isolate modifications made since a specified commit hash.

Related Skills

Explore More Software Engineering Skills→
probationer070probationer070

review

Review code against coding standards and functional specifications using Git.

Community
Advanced
CapplequoppeCapplequoppe

merge-completed-work-github

Create GitHub pull requests merging completed work branches into parent branches.

Community
Advanced
lehuuhau1231lehuuhau1231

lint-and-validate

Run linting and type checking across multiple programming ecosystems.

Community
Intermediate
jg-chalk-iojg-chalk-io

moai-docs-validation

Validate documentation against SPECs and MoAI-ADK standards.

Community
Intermediate