review

Identify and document code and infrastructure review findings with evidence references.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/ignidus/iscagent --skill review-ignidus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/ignidus/iscagent/tree/main/skills/review
Command: npx skills add https://github.com/ignidus/iscagent --skill review-ignidus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines pre-merge code and infrastructure reviews by enforcing evidence-backed findings, ensuring every claim has traceable references and context.

Core Features & Use Cases

  • Evidence-based findings with file/line references and test or evidence citations.
  • Two-pass review: prioritize critical issues first, followed by informational improvements.
  • Auto-classification of findings into actionable items and drift detection for scope changes.
  • Generates a structured findings report suitable for PR checks and governance.

Quick Start

Activate the review skill on a pull request to generate an evidence-based findings report.

Frequently Asked Questions about review

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

FAQPage Schema
How do I enforce evidence-based code review findings on pull requests?

Evidence-based code review findings are enforced by documenting issues with traceable file, line, and test references. A two-pass review prioritizes critical security and infrastructure issues first, followed by informational improvements, ensuring every claim has traceable context.

Can I conduct infrastructure review for Terraform changes before merging?

Infrastructure review for Terraform changes is supported during pre-merge pull request checks. The review identifies scope drift and documents infrastructure findings with evidence citations, generating a structured report suitable for governance and pre-merge validation.

What is the best way to automate pull request reviews for code and infrastructure?

Automating pull request reviews requires a two-pass workflow that auto-classifies findings into actionable items and handles obvious issues with auto-fixes. This generates a structured findings report with traceable evidence references for both code and infrastructure changes.

Does this pre-merge review process handle auto-fixing obvious code issues?

The pre-merge review process handles auto-fixing obvious code issues during its evidence-based workflow. It automatically classifies findings into actionable items and applies auto-fixes for straightforward problems before generating the final structured findings report.

How do I detect scope drift during a pull request review?

Scope drift detection during a pull request review is handled by auto-classifying findings and comparing them against the intended changes. The two-pass review ensures scope accuracy by documenting traceable issues and flagging deviations from the original pull request scope.

How do I generate a structured findings report for security and quality PR checks?

A structured findings report for security and quality PR checks is generated by conducting a two-pass evidence-based review. It documents code and infrastructure findings with file, line, and evidence citations, outputting a report suitable for automated PR checks and governance.