skills.rest
mujtaba3B
mujtaba3BCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

cr

Review local code changes and pull requests for merge readiness.

2|Updated May 13, 2026
Search Tags:#diff analysis#software engineering#code review#github#verification#pull requests#merge gate
One-click install
npx skills add https://github.com/mujtaba3B/gstack-extensions --skill cr-mujtaba3b
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cr
Source: https://github.com/mujtaba3B/gstack-extensions/tree/main/eng/skills/cr
Command: npx skills add https://github.com/mujtaba3B/gstack-extensions --skill cr-mujtaba3b

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a single, reliable path for reviewing code changes before merge, so local diffs and pull requests are evaluated consistently instead of bouncing between overlapping review tools.

Core Features & Use Cases

  • Risk-based review depth: It chooses a light, routine, or major review based on the scope and risk of the change.
  • Verified findings: It checks suspicious issues against the real repository before surfacing them, reducing false alarms.
  • Merge-gate support: It records the reviewed HEAD with a local stamp so the merge-clearance workflow can confirm that a genuine review happened.
  • Routing for the right workflow: It hands off someone else’s PR to the teammate-review path and existing review comments to the feedback-response paths.
  • Use Case: A developer wants to know whether their own branch is ready to merge, and this Skill inspects the diff, produces a verdict, and leaves behind the review record the gate expects.

Quick Start

Ask for a review of your local diff or pull request with /eng:cr so it scopes the change, selects the right review depth, verifies the findings, and records the merge-clearance stamp.

Frequently Asked Questions about cr

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

FAQPage Schema
How do I review local code changes for merge readiness?▼

You can review local code changes for merge readiness by scoping the diff, selecting a risk-based review depth, verifying findings against the repository, and recording a merge-clearance stamp for the reviewed HEAD.

How does risk-based code review work for high-risk changes like auth and migrations?▼

Risk-based code review evaluates the scope and risk of changes, applying a light, routine, or major review depth to effectively verify high-risk areas like auth, migrations, and concurrency before merge.

What is the best way to verify code review findings and reduce false alarms in pull requests?▼

The best way to verify code review findings is multi-lens verification against the real repository, which checks suspicious issues before surfacing them to reduce false alarms in pull requests.

Can I use a merge gate check for both personal diffs and pull requests?▼

Yes, you can use a merge gate check for personal diffs and pull requests; it records the reviewed HEAD with a local stamp so the merge-clearance workflow confirms a genuine review happened.

How do I handle code review feedback and existing review comments on a pull request?▼

Handle existing review comments by routing the pull request to the feedback-response path, which processes the feedback rather than starting a new review cycle from scratch.

Related Skills

Explore More Software Engineering Skills→
andrewthetechieandrewthetechie
2

code-review

Review code changes against a base branch for maintainability and structural issues.

Community
Advanced
zts212653zts212653
2.6k

merge-gate

Automate merge governance from gate checks to cleanup on Git main branches.

Community
Advanced
chokky-educationchokky-education

receiving-code-review

Standardizes incoming code review feedback verification and technical response preparation for pull requests and peer sessions.

Community
Intermediate
yonyon
3

lint

Run linters and static analysis tools with severity-based output and auto-fix mode.

Community
Basic