code-review

Automates structured code reviews for TypeScript pull requests and diffs.

4|2|Updated Aug 27, 2025

Search Tags:#typescript #security #safety #quality #static-analysis #code-review

Ready to run

npx skills add https://github.com/finger-gun/sisu --skill code-review-finger-gun

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/finger-gun/sisu/tree/main/packages/skills/skill-code-review
Command: npx skills add https://github.com/finger-gun/sisu --skill code-review-finger-gun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code Review skill helps teams assess safety, correctness, and maintainability across code changes.

Core Features & Use Cases

Analyzes changed files for invariants, edge cases, and potential security risks.
Validates input handling, error paths, and logging/scalability considerations.
Produces a structured, prioritized report with actionable remediation guidance for pull requests.

Quick Start

Run a structured code review on the current pull request.

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 TypeScript pull requests?▼

Automated code review for TypeScript pull requests works by scanning changed files to identify edge cases, security risks, and input validation failures. It then outputs a prioritized, structured report containing actionable remediation guidance.

What does static analysis check during a code review?▼

Static analysis during a code review checks for invariants, potential security risks, and maintainability issues across code changes. It validates input handling against schemas and evaluates error paths to ensure overall code safety and correctness.

Can I use this structured review to find security risks in changed files?▼

Yes, you can find security risks in changed files using this structured review. It analyzes code diffs to detect potential vulnerabilities, validates input handling against schemas, and assesses safety considerations across your project changes.

What is the best way to validate inputs against schemas in a pull request?▼

The best way to validate inputs against schemas in a pull request is to run an automated code review that explicitly checks functional requirements. It verifies input handling across changed files and emits a structured report highlighting any validation mismatches.

Does this code review approach work for non-TypeScript projects?▼

No, this code review approach is specifically applicable to TypeScript projects. It is designed to analyze TypeScript code changes to assess safety, correctness, and maintainability within that specific ecosystem and language environment.