deep-review

Audit code change sets and produce a final PR verdict.

2|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/Conava/claude-devline --skill deep-review-conava
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-review
Source: https://github.com/Conava/claude-devline/tree/main/skills/deep-review
Command: npx skills add https://github.com/Conava/claude-devline --skill deep-review-conava

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Final comprehensive pull request review ensures security, credentials, code quality, conventions, and plan compliance before merging, reducing risk and rework.

Core Features & Use Cases

  • Security Audit — vulnerability scanning and OWASP checks.
  • Credential Scan — detection of hardcoded keys, tokens, and secrets.
  • Code Quality & Conventions — debt assessment, error handling, and style adherence.
  • Plan Compliance & Verification — ensures acceptance criteria map to changes and tests pass.

Quick Start

Run the deep-review agent on a branch or PR and obtain a merge-readiness verdict.

Frequently Asked Questions about deep-review

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

FAQPage Schema
How do I automate pull request reviews for hardcoded credentials and security vulnerabilities?

Automated pull request reviews detect hardcoded credentials and security vulnerabilities by auditing code change sets against OWASP checks. This process scans git diffs to identify exposed tokens and secrets before producing a merge-readiness verdict.

What does a final PR code quality check include before merging a branch?

A final PR code quality check includes vulnerability scanning, credential detection, technical debt assessment, error handling verification, and style convention adherence. It ensures the code change set complies with defined acceptance criteria and passes all required tests.

Can I verify plan compliance and acceptance criteria automatically during a code review?

You can verify plan compliance automatically by mapping defined acceptance criteria directly against the code change set. The review process checks if the implemented changes fulfill the requirements and ensures all associated tests pass before merging.

Does a comprehensive PR security audit require static analysis results and git diff integration?

A comprehensive PR security audit requires integration with git diff and static analysis results to function effectively. These inputs provide the necessary code change context to perform vulnerability scanning, credential detection, and convention checks.

What is the best way to ensure secure merges across multiple repositories?

The best way to ensure secure merges across repositories is to apply a final review audit to branches and pull requests. This verifies security, credential safety, code quality, and plan compliance uniformly before allowing any code integration.

When should I use an automated code review audit instead of manual PR checks?

You should use an automated code review audit when you need consistent, final verification of security, credentials, and conventions across branches. Manual checks are prone to oversight, whereas an automated audit systematically enforces merge-readiness criteria.