sw-review

Analyze git diffs against project rules to identify vulnerabilities and compliance issues.

3|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/aydinsenturkk/stackwise --skill sw-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sw-review
Source: https://github.com/aydinsenturkk/stackwise/tree/main/skills/sw-review
Command: npx skills add https://github.com/aydinsenturkk/stackwise --skill sw-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of performing comprehensive code reviews by using project-specific rules and rulesets as checklists, ensuring code quality and security compliance.

Core Features & Use Cases

  • Automated Diff Analysis: Reads current git diffs, staged or unstaged, to identify changes needing review.
  • Rules and Profile Loading: Loads project rules based on .claude/profile.json and applies relevant rules depending on the changed files, enhancing review precision.
  • Structured Feedback: Provides organized, severity-based findings to guide developers before merging code changes.
  • Use Case: A developer pushes new code; this Skill analyzes the diff, identifies security vulnerabilities, architectural violations, and style issues, then outputs a prioritized review.

Quick Start

Review the latest changes in your project by running this Skill to automatically generate a detailed code review report.

Frequently Asked Questions about sw-review

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

FAQPage Schema
How do I automate code review for git diffs using project rules?

Automated diff analysis works by reading staged or unstaged git diffs, loading relevant rules based on the changed files, and generating structured feedback with severity-based findings to guide developers before merging.

Can I use custom rulesets for automated security checks on staged code changes?

Custom rulesets function as checklists during automated analysis, applying project-specific rules to the current code changes to detect compliance issues, architectural violations, and security vulnerabilities.

What is the best way to identify security vulnerabilities before merging code?

Running a rule-based automated analysis on your git diff is the best way to find vulnerabilities, as it evaluates code changes against defined project rulesets to detect security issues and architectural violations.

Does this automated code analysis require a specific profile configuration?

This automated code analysis requires a `.claude/profile.json` file to load project rules, which ensures the relevant rulesets are applied accurately depending on the specific files changed in the diff.

How does automated diff analysis handle architectural violations?

Automated diff analysis detects architectural violations by evaluating code changes against loaded project rulesets, identifying structural compliance issues, and reporting them through structured, severity-based findings.

When do I need to run automated code quality checks on a diff?

You need to run automated code quality checks on a diff whenever you push new code, ensuring that security vulnerabilities, architectural violations, and style issues are caught and prioritized before merging.