requesting-code-review

Scan code for security concerns and quality issues before committing.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/LynxLabVN/office-agent --skill requesting-code-review-lynxlabvn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/LynxLabVN/office-agent/tree/main/agent-core/skills/software-development/requesting-code-review
Command: npx skills add https://github.com/LynxLabVN/office-agent --skill requesting-code-review-lynxlabvn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures code quality and security by running static scans, baseline tests, and code reviews before committing code changes.

Core Features & Use Cases

  • Static Security Scan: Detects security concerns in code such as hardcoded secrets, shell injection, and SQL injection.
  • Baseline Tests and Linting: Ensures code quality by comparing new changes against baseline results from tests and linting.
  • Independent Reviewer Subagent: Uses a separate context for reviewing code changes to ensure impartiality.
  • Auto-Fix Loop: Provides automated fixes for identified issues and allows for up to two fix-and-reverify cycles.
  • Committing Changes: Successfully completes the verification process allows code changes to be committed with a verified prefix.
  • Use Case: Ideal for developers who want to ensure their code adheres to security standards and quality gates before pushing to a repository.

Quick Start

Run the requesting-code-review skill to verify your code changes before committing.

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 static security scan and code quality check before committing changes?

Pre-commit code review verifies code changes by executing static security scans, baseline tests, and linting. It detects hardcoded secrets, shell injection, and SQL injection while ensuring new changes meet quality standards before you commit.

What is the best way to automatically fix security issues and linting errors found during a pre-commit review?

An auto-fix loop provides automated fixes for identified code review issues and allows up to two fix-and-reverify cycles. This ensures your code changes pass quality gates and security scans before final approval.

Can I use an independent reviewer context to check code changes for security concerns?

Yes, pre-commit code review uses an independent reviewer subagent with a separate context. This ensures impartial reviews of code changes for security concerns and quality issues before committing.

Does pre-commit code review require manual intervention after running static scans and baseline tests?

Pre-commit code review requires multiple steps including code scanning, test execution, and manual review. After static scans and baseline tests run, a manual review step ensures adherence to security and quality standards before committing.

How does a verified prefix work when committing code changes after a quality gate review?

Successfully completing the pre-commit verification process allows code changes to be committed with a verified prefix. This prefix indicates the changes passed static security scans, baseline tests, and code reviews.

What are the limitations of the auto-fix loop during pre-commit code reviews?

The auto-fix loop limitation is that it allows for up to two fix-and-reverify cycles only. If code changes still fail static scans or baseline tests after two automated fixes, manual intervention is required to pass quality gates.