allbeingsfuture/skills@code-review

Reviews local git diffs and remote Pull Requests for correctness, security, and maintainability issues.

9|2|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/AllBeingsFuture/AllBeingsFuture --skill allbeingsfuture-skills-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: allbeingsfuture/skills@code-review
Source: https://github.com/AllBeingsFuture/AllBeingsFuture/tree/main/electron/embedded-assets/skills/code-review
Command: npx skills add https://github.com/AllBeingsFuture/AllBeingsFuture --skill allbeingsfuture-skills-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers and reviewers catch correctness, security, and maintainability issues before merging by providing a structured review workflow for both local changes and remote Pull Requests.

Core Features & Use Cases

  • Target resolution: Handles remote Pull Requests by ID or URL and local changes including staged and working-tree diffs.
  • Preparation guidance: Recommends checkout and preflight verification steps and reading PR context to reduce false positives.
  • In-depth analysis pillars: Evaluates correctness, maintainability, readability, efficiency, security, edge-case handling, and test coverage.
  • Actionable feedback: Produces a concise summary, categorized findings (Critical / Improvements / Nitpicks), and a clear approval or request-changes recommendation.
  • Cleanup reminder: Suggests switching back to the default branch after remote PR review.

Quick Start

Ask the agent to review my changes or a Pull Request URL or number and return a summary, categorized findings, and a clear approval or request-changes recommendation.

Frequently Asked Questions about allbeingsfuture/skills@code-review

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

FAQPage Schema
How do I review a GitHub pull request for security and maintainability issues?

To review a pull request for security and maintainability, provide the PR number or URL to obtain a structured analysis covering correctness, edge-case handling, and test coverage, returning categorized findings and an approval recommendation.

Can I run a code review on local git diffs before opening a pull request?

Yes, you can review local git diffs by applying the code review to staged or working-tree changes. It analyzes correctness, readability, and efficiency to produce categorized findings and a clear request-changes or approval recommendation.

Do I need the GitHub CLI to review remote pull requests?

The GitHub CLI is optionally required for remote pull request checkout during code review. You also need repository access, git tools, and the ability to run project verification scripts like preflight test suites.

What is the best way to categorize code review findings for a diff?

The best way to categorize code review findings is separating them into Critical, Improvements, and Nitpicks. This structured feedback approach highlights correctness and security issues alongside maintainability and readability suggestions.

How does preflight verification reduce false positives in code review?

Preflight verification reduces false positives in code review by running project test suites and reading PR context before analysis. Checking out remote PRs ensures the review evaluates the exact code state for accurate correctness and security findings.