skills.rest
probationer070
probationer070COMMUNITY
Explore all skills by this author →
GitHub

review

Review code against coding standards and functional specifications using Git.

Updated May 30, 2026
Search Tags:#code review#repository management#specification compliance#standards compliance#parallel review
One-click install
npx skills add https://github.com/probationer070/Cloud-Project --skill review-probationer070
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/probationer070/Cloud-Project/tree/main/.claude/skills/review
Command: npx skills add https://github.com/probationer070/Cloud-Project --skill review-probationer070

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the code review process by providing a parallel assessment of code against both coding standards and functional specifications.

Core Features & Use Cases

  • Parallel Review: Simultaneously evaluates code for adherence to coding standards and compliance with specifications.
  • Standards Compliance: Checks for adherence to documented coding standards within the repository.
  • Spec Compliance: Ensures that the code meets the requirements outlined in the originating issue or PRD.
  • Use Case: Ideal for reviewing pull requests, branch changes, or any codebase modifications where both standards and specifications need to be validated.

Quick Start

Run the review skill to get a comprehensive code review report for your current branch.

Frequently Asked Questions about review

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

FAQPage Schema
How do I conduct a parallel code review for standards and specifications?▼

A parallel code review simultaneously evaluates code against documented coding standards and originating functional specifications. It analyzes commit history, standards documentation, and spec sources using Git to ensure branch changes meet repository requirements.

What is the best way to check if my pull request meets both coding standards and PRD specifications?▼

Checking pull request compliance involves running a parallel review that validates code against both repository standards and product requirement documents. This ensures branch modifications satisfy documented rules and originating functional requirements concurrently.

Can I validate specification compliance using local repository files and commit history?▼

Yes, specification compliance can be validated by analyzing local repository files and Git commit history. The review process cross-references code changes against originating spec sources and documented standards within the repository.

Do I need Git to perform a parallel review of branch changes?▼

Yes, Git is required to perform a parallel review of branch changes. The review process utilizes Git and local repository files to analyze commit history and ensure modifications comply with repository standards and specifications.

How does a parallel code review differ from standard repository management checks?▼

A parallel code review differs by simultaneously evaluating both specification compliance and coding standards, rather than sequentially. It cross-references originating requirements and documented standards against commit history to provide a comprehensive compliance report.

What should I review in my codebase to ensure standards compliance before merging?▼

To ensure standards compliance before merging, review your codebase against documented coding standards and originating functional specifications. Analyze local repository files and commit history to verify branch changes meet repository requirements.

Related Skills

Explore More Software Engineering Skills→
JohnRobert-OlanoJohnRobert-Olano

review

Audits latest commits for coding-standards compliance and specification accuracy.

Community
Advanced
Obsidian-OwlObsidian-Owl
4

speckit-merge-check

Detect contract changes, merge conflicts, and architecture compliance issues on Epic branches.

Official
Advanced
martimramosmartimramos
1

forge-conventions

Standardizes git commits, branch names, and code style via configurable rules.

Community
Basic
protofireprotofire
3

protofire-qa-agent

Audit smart contracts with Slither, Echidna, and Foundry fuzz testing.

Official
Advanced