review

Cross-references GitHub pull requests with project specs and architecture docs.

1|Updated Jul 1, 2026
One-click install
npx skills add https://github.com/marcuskrogh/skills --skill review-marcuskrogh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/marcuskrogh/skills/tree/main/skills/review
Command: npx skills add https://github.com/marcuskrogh/skills --skill review-marcuskrogh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the inconsistency and cognitive load of manual code reviews by providing a structured, multi-axis analysis of pull requests that ensures architectural integrity, correctness, and adherence to standards.

Core Features & Use Cases

  • Multi-Axis Analysis: Evaluates code across five distinct dimensions: Spec, Correctness, Integration, Architecture, and Standards.
  • Automated Feedback: Posts structured findings directly to GitHub PRs and tracks progress on pipeline issues.
  • Use Case: When a developer submits a complex feature branch, this skill automatically cross-references the code against the project's architecture docs and issue requirements to identify structural regressions or integration gaps before a human reviewer even opens the PR.

Quick Start

Invoke the review skill by providing the issue key for the pull request you want to analyze.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate GitHub PR code reviews against architectural documentation?

Automated GitHub PR code reviews cross-reference pull request changes against project specifications, architectural documentation, and integration contracts. This skill evaluates code across five dimensions: Spec, Correctness, Integration, Architecture, and Standards to identify regressions before human review.

What is multi-axis analysis in automated pull request reviews?

Multi-axis analysis in automated pull request reviews evaluates code changes across five distinct dimensions: Spec, Correctness, Integration, Architecture, and Standards. This structured approach reduces manual cognitive load by validating code correctness and adherence to established coding standards automatically within development pipelines.

How do I run a code review on a pull request using an issue key?

To run a code review on a pull request, invoke the review skill by providing the issue key associated with the target pull request. The skill requires authenticated access to GitHub APIs and project tracker backends to correlate PR diffs with defined work packages and architectural requirements.

Do I need authenticated GitHub API access to automate pull request code reviews?

Yes, authenticated GitHub API access is required to automate pull request code reviews. The process also requires access to project-specific tracker backends to successfully correlate pull request changes with defined work packages, integration contracts, and architectural requirements.

What's the best way to check pull requests for integration gaps before human review?

The best way to check pull requests for integration gaps before human review is using automated multi-axis analysis. By cross-referencing feature branch code against architecture docs and issue requirements, the system identifies structural regressions and integration gaps early in the software development pipeline.

Are there limitations when using automated code reviews for complex feature branches?

A limitation of automated code reviews for complex feature branches is the strict dependency on project-specific tracker backends and architectural documentation. Without authenticated access to these systems to correlate PR diffs with defined work packages, the multi-axis review cannot validate integration contracts or spec adherence.