requesting-code-review

Verify staged git changes with security scans and baseline-aware tests.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/devMoez/titan --skill requesting-code-review-devmoez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/devMoez/titan/tree/main/skills/software-development/requesting-code-review
Command: npx skills add https://github.com/devMoez/titan --skill requesting-code-review-devmoez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents insecure or broken code from being committed by running a pre-commit verification pipeline on your pending changes.

Core Features & Use Cases

  • Static security scan: Detects high-risk patterns in the added diff (e.g., hardcoded secrets, shell injection, eval/exec, unsafe deserialization).
  • Baseline-aware quality gates: Runs tests and lint/type checks when possible and blocks only regressions relative to a baseline.
  • Independent reviewer subagent: Delegates a fail-closed review to validate the diff from a fresh context, then optionally guides auto-fix.

Quick Start

Run requesting-code-review when prompted before you commit or push your changes, for example after implementing a feature and staging files with git add.

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 security scan on staged git changes?

A pre-commit security scan inspects staged git diffs to detect hardcoded secrets, shell injection, eval/exec, and unsafe deserialization in added lines before committing.

What is baseline-aware regression testing for code reviews?

Baseline-aware regression testing runs tests and lint/type checks on staged changes, blocking commits only when new regressions appear relative to an established quality baseline.

Can I automatically fix broken code before pushing a git commit?

Yes, an independent reviewer subagent validates the diff from a fresh context, then optionally guides a fail-closed auto-fix loop to correct broken code before pushing.

Does pre-commit linting block all errors or only new regressions in the git diff?

Pre-commit linting blocks only new regressions relative to a baseline, running quality gates when possible to ensure safer code submissions without failing on pre-existing issues.

What's the best way to verify a bug fix safely before it lands?

Verify a bug fix safely by running a pre-commit pipeline that inspects staged git diffs, executes static security scans, counts baseline regressions, and parses an independent reviewer verdict.

When do I need an independent diff reviewer for git changes?

You need an independent diff reviewer for feature work and bug fixes to validate staged git changes from a fresh context, providing a fail-closed JSON verdict before code lands.