code-review

Analyze code diffs against stories, tests, and coding standards.

1|Updated Dec 31, 2025

Search Tags:#linting #OWASP #maintainability #static-analysis #code-review #pull-request

Ready to run

npx skills add https://github.com/tomas-u/claude-skills --skill code-review-tomas-u

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide thorough, constructive code reviews that identify defects, security gaps, and maintainability issues across PRs and commits.

Core Features & Use Cases

Story alignment verification: Ensure changes map to requirements and linked stories.
Code quality & readability checks: Enforce naming, structure, and clean code practices.
Security analysis (OWASP): Identify common vulnerabilities and provide actionable remediation.
Feedback & traceability: Create actionable, concrete recommendations with reasoning.

Quick Start

Review a PR by supplying the diff, the PR link, and the related stories; the skill will output a structured review report.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I automate code reviews for pull requests to check story alignment and security?▼

Automate code reviews by analyzing pull request diffs against linked stories, tests, and coding standards. This process verifies requirement alignment, identifies OWASP security gaps, and generates actionable feedback for pull requests and commits.

What static analysis checks are needed to enforce maintainability and clean code standards in a PR?▼

Static analysis checks for maintainability enforce naming conventions, code structure, and readability standards. By analyzing diffs against project linting rules, the review identifies defects and generates concrete recommendations to improve overall code quality.

Can I identify OWASP vulnerabilities directly from a git diff before merging a commit?▼

Yes, you can identify OWASP vulnerabilities from a git diff before merging. Security analysis checks the diff against project security guidelines to detect common vulnerabilities and provides actionable remediation steps directly in the review report.

What information do I need to provide to run an automated code review on a pull request?▼

To run an automated code review, you must provide the pull request diff, the PR link, and related user stories. Access to project conventions like linting rules, test coverage metrics, and security guidelines is also required to generate feedback.

Does automated code review work without pre-configured project linting rules and test coverage metrics?▼

No, automated code review requires access to project conventions including linting rules, test coverage, and security guidelines. Without these coding standards, the review cannot accurately evaluate code quality, maintainability, or story alignment.

How does a code review skill ensure feedback is actionable and traceable for developers?▼

The code review ensures actionable feedback by generating concrete recommendations with clear reasoning based on the diff analysis. It maps code changes directly to requirements and quality gates, making every identified defect or security gap fully traceable.