code-review

Name: code-review
Availability: InStock
Author: TokenOverflow

Review pull requests for coding standards, test coverage, and security issues.

Updated Jan 31, 2026

Search Tags:#security #quality-assurance #coding-standards #code-review #unit-tests #integration-tests

Ready to run

npx skills add https://github.com/token-overflow/tokenoverflow --skill code-review-token-overflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/token-overflow/tokenoverflow/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/token-overflow/tokenoverflow --skill code-review-token-overflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The code-review skill ensures that changes are thoroughly vetted after implementation, preventing quality regressions and security issues.

Core Features & Use Cases

Enforces consistent coding practices and architecture alignment.
Validates test coverage and detects edge-case scenarios.
Use Case: When a PR lands, trigger this review to catch potential bugs and ensure compliance with project standards.

Quick Start

Review the latest changes in a pull request and generate a deterministic feedback 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 review for pull requests to prevent quality regressions?▼

Automated code review for pull requests prevents quality regressions by enforcing consistent coding practices, validating test coverage, and running security checks. It generates a deterministic feedback report aligned with project guidelines to catch potential bugs before merging.

What does a deterministic code review process check for in software engineering?▼

A deterministic code review process checks for coding standards compliance, architecture alignment, and test coverage for edge-case scenarios. It ensures traceable findings by validating that code changes pass review steps without introducing security issues or functional regressions.

How can I validate unit test coverage and security checks before merging a PR?▼

Validate unit test coverage and security checks before merging a PR by triggering an automated review process. This ensures code changes pass deterministic review steps, detects edge-case scenarios, and confirms alignment with project guidelines and tests to prevent regressions.

Does automated code review work without predefined project guidelines and coding standards?▼

Automated code review requires predefined project guidelines and coding standards to function effectively. Without these baseline rules, the deterministic review steps cannot enforce architecture alignment, validate test coverage, or generate a traceable feedback report ensuring code compliance.

What is the best way to catch security issues and edge-case scenarios during code changes?▼

The best way to catch security issues and edge-case scenarios during code changes is applying a structured review skill. It enforces coding practices, validates test coverage, and performs security checks to generate traceable findings aligned with project standards.

When should I not rely on automated PR reviews for maintaining code quality?▼

You should not rely on automated PR reviews when project guidelines or test suites are undefined, as the deterministic review steps require these baselines to validate coverage, enforce coding standards, and generate traceable findings without regressions.