skills.rest
babually
babuallyCOMMUNITY
Explore all skills by this author →
GitHub

review

Review code changes against repository standards and originating specifications.

1|Updated Jun 27, 2026
Search Tags:#diff analysis#code review#pull request#standards#spec compliance#branch review
One-click install
npx skills add https://github.com/babually/bongo-template --skill review-babually
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/babually/bongo-template/tree/main/.agents/skills/review
Command: npx skills add https://github.com/babually/bongo-template --skill review-babually

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you assess a code change from two independent angles at once: whether it follows the repository’s documented standards and whether it matches the originating spec or issue.

Core Features & Use Cases

  • Standards Review: Checks a diff against repo guidance such as coding conventions, architecture notes, and style documents.
  • Spec Review: Compares the implemented change to the requested behavior in a PRD, issue, or spec file.
  • Side-by-Side Reporting: Produces separate findings for standards and spec so you can quickly see where a change is compliant, off-scope, or incomplete.
  • Use Case: Ask for a review of a branch, pull request, or work in progress when you want a structured critique before merging.

Quick Start

Ask the assistant to review your branch against the specified base branch or commit and include the relevant spec if you have one.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a pull request against coding standards and a spec?▼

To review a pull request, compare the code diff between HEAD and a fixed reference point against repository standards and the originating specification to identify violations, missing behavior, and scope creep.

Can I check a work-in-progress branch for spec compliance before merging?▼

Yes, you can check a work-in-progress branch for spec compliance by evaluating the diff against the requested behavior in a PRD, issue, or spec file to ensure the implementation is complete and correct.

What is the best way to automate code review for branch diffs?▼

Automating code review for branch diffs involves comparing changes against documented coding conventions and architecture notes, producing side-by-side reports for standards violations and spec deviations.

Does diff analysis work without a specification document?▼

Diff analysis requires a spec source to evaluate requirement compliance, so without a specification document, the review can only assess whether the changes follow repository standards and coding conventions.

When do I need to run a separate quality and spec compliance check?▼

You need a separate quality and spec compliance check when merging a branch, pull request, or work-in-progress diff to independently verify repository standards adherence and originating specification alignment.

Why does my code review show scope creep in the diff?▼

Your code review shows scope creep because the diff analysis compares the implemented changes against the originating specification, flagging any functionality that exceeds the requested behavior in the PRD or issue.

Related Skills

Explore More Software Engineering Skills→
ruskibeatsruskibeats

review

Review code diffs against coding standards and specifications.

Community
Advanced
nikhilsitaramnikhilsitaram
89

pr-merge

Merge reviewed GitHub pull requests and clean up branches and worktrees.

Community
Advanced
ghufronbagaskaraghufronbagaskara

requesting-code-review

Automate pre-commit code verification with static security analysis, regression testing, and subagent review.

Community
Advanced
rafaelromaorafaelromao
5

sandman-self-review

Review code changes against coding standards and specification adherence.

Community
Advanced