requesting-code-review

Run static security scans, baseline quality gates, and auto-fix loops before git commits.

2.8k|332|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/moltis-org/moltis --skill requesting-code-review-moltis-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/moltis-org/moltis/tree/main/crates/skills/src/assets/software-development/requesting-code-review
Command: npx skills add https://github.com/moltis-org/moltis --skill requesting-code-review-moltis-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-commit verification pipeline detects and blocks problematic changes by running static security scans, applying baseline-aware quality gates, and coordinating an independent reviewer subagent with an auto-fix loop before code lands.

Core Features & Use Cases

  • Static security scans run on diffs and staged changes prior to commit.
  • Baseline-aware quality gates ensure adherence to project standards with auto-fix assistance.
  • Independent reviewer subagent provides external review to prevent self-verification.
  • Auto-fix loop automates safe fixes to reduce repetitive toil.
  • Workflow coverage supports commits, pushes, and PR preparation across typical git workflows.

Quick Start

Run the pre-commit verification after making changes and before committing or pushing to your branch.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I automate pre-commit code review and static scans before pushing changes?

Automated pre-commit code review runs static security scans, baseline tests, and linting on staged changes and diffs before git commit. An independent reviewer subagent evaluates the changes while an auto-fix loop safely resolves repetitive issues to block problematic code from landing.

What is baseline-aware linting and how does it work for local development?

Baseline-aware linting enforces project quality standards by evaluating only new or modified code against established baselines. It runs during pre-commit verification on staged changes, ensuring incremental edits adhere to rules without flagging pre-existing issues across multi-file edits.

Can I run static security scans on staged diffs across different programming languages and repos?

Static security scans run on staged changes and diffs across languages and repos during pre-commit verification. They apply to local development work before commits, pushes, or pull requests, detecting vulnerabilities in modified code before it lands.

How do I prevent self-verification when automating code review before a git commit?

An independent reviewer subagent prevents self-verification by separately evaluating changes made during local development. Guardrails ensure the verifier never audits its own work, maintaining objective pre-commit code verification across diffs and multi-file edits.

Does the auto-fix loop handle linting and static scan errors automatically?

The auto-fix loop automates safe fixes for linting and static scan issues detected during pre-commit verification. It reduces repetitive toil by safely resolving detected problems on staged changes before the independent reviewer subagent performs its final evaluation.

When should I use an automated pre-commit verification pipeline instead of manual code review?

Use pre-commit verification when you need to consistently block problematic changes before they enter version control. It automates static security scans, baseline-aware quality gates, and independent review across commits, pushes, and pull requests, reducing manual review burden for multi-file edits.