ada-requesting-code-review

Runs pre-commit security scans, tests, linting, and independent reviewer checks on git diffs.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/wubing7755/Ada --skill ada-requesting-code-review-wubing7755
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ada-requesting-code-review
Source: https://github.com/wubing7755/Ada/tree/main/skills/software-development/ada-requesting-code-review
Command: npx skills add https://github.com/wubing7755/Ada --skill ada-requesting-code-review-wubing7755

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code often gets committed without verification, letting secrets, injection vulnerabilities, regressions, and logic errors slip into the repository. This Skill enforces a structured pre-commit review pipeline so every change is scanned, tested, and independently reviewed before it lands. ## Core Features & Use Cases - Static Security Scanning: Greps added diff lines for hardcoded secrets, shell injection, eval/exec, unsafe pickle deserialization, and SQL string formatting. - Baseline-Aware Quality Gates: Runs pytest, npm test, cargo test, or go test plus ruff, mypy, eslint, tsc, clippy, or go vet, comparing failures against a pre-change baseline so only new regressions block the commit. - Independent Reviewer Subagent: Dispatches a fresh-context reviewer via delegate_task with fail-closed JSON verdicts, then an auto-fix agent with a maximum of two fix-and-reverify cycles. - Use Case: After finishing a feature touching three files, ask for a review before committing; the Skill inspects the staged diff, flags a hardcoded API key, runs the test suite, gets a PASS verdict from the independent reviewer, and commits with a [verified] prefix. ## Quick Start Ask the agent to review your staged changes and run all relevant checks before committing.

Frequently Asked Questions about ada-requesting-code-review

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

FAQPage Schema
How do I review my code before committing with git?

Stage your changes with git add, then ask for a pre-commit review. The pipeline inspects the staged diff, scans added lines for secrets and injection patterns, runs the project's tests and linters, and gets an independent reviewer verdict before committing.

How to scan a git diff for hardcoded secrets and security issues?

The scan greps added lines in the diff for patterns like api_key, secret, password, and token assignments, plus os.system, subprocess with shell=True, eval, exec, pickle.loads, and string-formatted SQL queries. Any match is treated as a security concern fed into the reviewer.

What is the difference between this pre-commit review and github-code-review?

This Skill verifies your own local changes before committing, while github-code-review reviews other people's pull requests on GitHub with inline comments. Use this one for pre-push verification, not remote PR feedback.

Does the pre-commit pipeline support Python, Node, Rust, and Go projects?

Yes. It auto-detects the project type and runs pytest, npm test, cargo test, or go test, plus ruff, mypy, eslint, tsc, clippy, or go vet when installed. Missing tools are skipped silently without failing the run.

What happens when the automated review finds failures?

Failures are reported by category, then a separate fix agent corrects only the listed issues and the full verification cycle re-runs. After two failed fix attempts, the remaining issues are escalated to the user with suggestions like git stash or git reset.

When should I skip pre-commit verification?

Skip it for documentation-only changes, pure configuration tweaks, or when you explicitly say to skip verification. It also stops when the diff is empty, the directory is not a git repository, or verification would require destructive actions or credentials.