requesting-code-review

Reviews git diffs for security issues and EVA invariants before committing changes.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/raulisai/eva02 --skill requesting-code-review-raulisai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/raulisai/eva02/tree/main/apps/eva-core/src/skills/software-development/requesting-code-review
Command: npx skills add https://github.com/raulisai/eva02 --skill requesting-code-review-raulisai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It catches security flaws, leaked secrets, and violations of EVA platform invariants before code is committed, pushed, or marked complete. ## Core Features & Use Cases - Pre-commit Checklist: Inspects git status and diffs for secrets, debug code, broad exception swallowing, unsafe shell execution, and dependency churn. - EVA Invariant Verification: Confirms tenant data is scoped by org_id, RLS changes live in 014_rls_policies.sql, sensitive actions use the Approval Engine, and route boundaries stay correct. - Tiered Test Strategy: Runs focused tests first, then broader suites, including RLS_TEST=true npm run test:e2e when RLS behavior changed. - Use Case: After implementing a new NestJS endpoint, run this review to verify tenant isolation and summarize findings, fixes, and residual risk before delivery. ## Quick Start Ask the agent to run a pre-commit code review of the current git changes against the EVA security and tenancy checklist.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I review code changes before committing in git?

Run git status --short and git diff to inspect modified files, then check for secrets, debug code, and unsafe patterns. This skill formalizes that review with a checklist and test commands before you commit or push.

How to check for leaked secrets in a git diff?

Inspect the full diff with git diff and look for hardcoded credentials, API keys, or environment values. The review checklist explicitly flags secrets alongside debug code and unsafe shell execution.

What should a pre-commit security review checklist include?

It should cover secret detection, broad exception swallowing, unsafe shell execution, dependency churn, and project-specific invariants. For EVA, that includes org_id tenant scoping, RLS policy placement, and Approval Engine usage.

When should I run RLS tests in Supabase projects?

Run RLS-focused end-to-end tests whenever row-level security behavior changes. In EVA, use RLS_TEST=true npm run test:e2e with real Supabase test credentials configured.

Does this review skill push or merge code automatically?

No. It only reviews and verifies changes; it does not push, merge, deploy, or mutate external systems without explicit approval, per the EVA Runtime Skill Policy.