review

Review code diffs for security risks and shell script quality.

2|Updated Apr 6, 2017

Search Tags:#automation #git #security #quality #review #shellcheck #code

Ready to run

npx skills add https://github.com/shiiman/dotfiles --skill review-shiiman

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the process of reviewing code changes by surfacing security risks, shell script quality concerns, and compatibility issues, enabling faster, safer releases.

Core Features & Use Cases

Diff analysis across branches, including default branch diffs, staged changes, and unstaged changes.
Security checks (credential exposure, command injection risk) and shell script quality assessments (lint-like checks, proper quoting, error handling).
Use Case: when evaluating a feature branch or pull request, quickly identify critical issues and generate actionable improvement suggestions.

Quick Start

Run the review on the target changes to receive a security, shell-script quality, and compatibility assessment.

Frequently Asked Questions about review

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

FAQPage Schema

How do I automate code reviews for security risks in git diffs?▼

Automated code review scans git diffs to surface security risks like credential exposure and command injection. It analyzes staged, unstaged, or branch changes to produce a structured assessment with actionable improvement suggestions.

How does shell script quality checking work for staged changes?▼

Shell script quality checking reviews staged changes for unsafe eval usage, proper quoting, and error handling. It applies lint-like assessments to shell scripts within the code changes to identify compatibility and quality concerns.

Can I run a security review on specific file paths instead of the full diff?▼

Security review supports optional targeting via file paths. You can apply checks to specific files instead of analyzing the full diff, focusing the assessment on credential exposure and sanitized inputs only where needed.

What's the best way to check for credential exposure in a feature branch?▼

The best way to check for credential exposure in a feature branch is running an automated review against the default branch diff. This surfaces security risks, shell script quality issues, and compatibility concerns for faster releases.

Does automated code review detect command injection risks in shell scripts?▼

Automated code review detects command injection risks by checking for unsafe eval usage and unsanitized inputs in shell scripts. It enforces security checks across code changes and generates structured improvement suggestions.

When should I not use automated code review for my code changes?▼

Automated code review is limited to security, shell script quality, and compatibility checks. It should not replace human review for complex architectural decisions, business logic validation, or performance assessment of code changes.