review

Analyzes git diffs and generates prioritized code review feedback before integration.

Updated Jan 26, 2026

Search Tags:#automation #performance #security #static-analysis #lint #code-review #git-diff

Ready to run

npx skills add https://github.com/mgoodman60/foremanos --skill review-mgoodman60

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/mgoodman60/foremanos/tree/main/.claude/skills/review
Command: npx skills add https://github.com/mgoodman60/foremanos --skill review-mgoodman60

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers quickly identify issues introduced by recent changes and provide actionable feedback to improve code quality before merging.

Core Features & Use Cases

Automated change analysis: Review diffs to surface security, performance, style, error handling, and test coverage issues.
Actionable feedback & checklists: Generate concise, prioritized recommendations aligned with a review checklist.
Use Case: When preparing a pull request, run this Skill to produce a focused report that highlights critical defects and suggested fixes for the codebase.

Quick Start

Review the current changeset to generate an actionable feedback report.

Frequently Asked Questions about review

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

FAQPage Schema

How do I automate code review for pull requests using git diffs?▼

Automated code review analyzes recent git diffs to identify security, performance, style, error handling, and test coverage issues, generating actionable feedback and prioritized recommendations before integration.

What is static analysis for code changes and when do I need it?▼

Static analysis for code changes evaluates recent commits to surface defects and improve code quality. You need it before merging pull requests to ensure security, performance, and style issues are caught early.

Can I use automated lint and security checks across different codebases?▼

Yes, automated lint and security checks apply to pull requests and commits across codebases. The skill requires access to git diffs and static analysis tooling to evaluate changes regardless of the specific codebase.

What's the best way to generate a code review checklist for recent commits?▼

The best way to generate a code review checklist is to run an automated analysis on the current changeset. This produces a focused, prioritized report highlighting critical defects and suggested fixes aligned with review standards.

Does automated code review replace manual pull request evaluation?▼

Automated code review supplements manual evaluation by quickly surfacing security, performance, and test coverage issues from git diffs. It provides actionable feedback and checklists, but developers still make final merge decisions.

Why does my static analysis report miss test coverage issues in my git diff?▼

Static analysis reports may miss test coverage issues if the tooling lacks access to the full git diff context. Ensure the skill has complete access to recent changesets and static analysis tools to properly evaluate coverage.