skills.rest
TitoPrausee
TitoPrauseeCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Verify staged git changes for security issues, regressions, and logic errors.

Updated Jul 7, 2026
Search Tags:#git#testing#code review#linting#auto-fix#pre-commit#security scan
One-click install
npx skills add https://github.com/TitoPrausee/nexus-toti --skill requesting-code-review-titoprausee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/TitoPrausee/nexus-toti/tree/main/data/skills/software-development/requesting-code-review
Command: npx skills add https://github.com/TitoPrausee/nexus-toti --skill requesting-code-review-titoprausee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unsafe or broken code from being committed by running a structured pre-commit verification workflow that checks for security issues, regressions, and logic mistakes.

Core Features & Use Cases

  • Diff Inspection: Reviews staged and unstaged changes to understand exactly what is being introduced.
  • Security Scanning: Flags hardcoded secrets, shell injection, unsafe eval or exec usage, unsafe deserialization, and SQL injection patterns.
  • Baseline-Aware Testing: Compares current test and lint results against the project baseline so only new failures block progress.
  • Independent Review Loop: Uses a separate reviewer perspective and an auto-fix cycle to catch issues the implementer may miss.
  • Use Case: Ideal after finishing a feature, fixing a bug, or preparing a pull request when you want a production-style quality gate before commit or push.

Quick Start

Use the requesting-code-review skill to verify the current git changes before committing and report any security, test, lint, or logic problems.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I run a pre-commit code review to catch security issues and regressions?▼

Run a pre-commit code review to inspect staged git diffs, scan for hardcoded secrets and SQL injection, run baseline-aware tests, and validate logic before committing changes safely.

How does baseline-aware testing work when verifying staged code changes?▼

Baseline-aware testing compares current test and lint results against the project baseline, ensuring only new failures introduced by your staged changes block the commit process.

Can I automatically fix blocking linting and security scan issues before a git commit?▼

Yes, an independent reviewer validation and auto-fix loop identifies blocking issues like unsafe eval usage or shell injection and automatically attempts fixes before the commit.

What is the best way to scan staged git changes for hardcoded secrets and SQL injection?▼

The best way to scan staged git changes is using a structured pre-commit workflow that performs diff inspection and security scanning to flag hardcoded secrets, unsafe deserialization, and SQL injection patterns.

When do I need to use an independent reviewer loop for code review?▼

You need an independent reviewer loop after finishing feature work, bug fixes, or multi-file edits to catch logic errors the implementer missed before preparing a pull request.

Related Skills

Explore More Software Engineering Skills→
elsolalelsolal
1

code-reviewer

Analyze git diffs, lint results, and test outcomes across three review passes.

Community
Intermediate
bdsqqqbdsqqq
59

git-ship

Stage modified files, commit with conventional commits, and push to the remote repository.

Community
Intermediate
kzinmrkzinmr
7

requesting-code-review

Automate pre-commit code review with static analysis, security scanning, and automated fixes.

Community
Advanced
HuskyDannyHuskyDanny

requesting-code-review

Automate pre-commit code review with static security scanning and auto-fix loops.

Community
Advanced