reviewing

Name: reviewing
Availability: InStock
Author: djwmobley

Review changed files against pipeline.yml rules and generate structured findings.

Updated Mar 18, 2026

Search Tags:#security #engineering #static-analysis #quality-assurance #code-review #diff-review

Ready to run

npx skills add https://github.com/djwmobley/pipeline --skill reviewing-djwmobley

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reviewing
Source: https://github.com/djwmobley/pipeline/tree/main/skills/reviewing
Command: npx skills add https://github.com/djwmobley/pipeline --skill reviewing-djwmobley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill standardizes per-change quality reviews by applying configurable criteria to code diffs, ensuring consistent, evidence-based findings and filtering out non-actionable decisions.

Core Features & Use Cases

Load non-negotiable decisions from pipeline.yml to prevent flagging intentional architectural choices.
Run static analysis and SAST checks, diff analysis, and context-aware reviews of changed files.
Produce structured findings with severity, file path, line number, rule ID, and actionable fixes for remediation.

Quick Start

Run the review command against the feature branch to generate a findings report.

Frequently Asked Questions about reviewing

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

FAQPage Schema

How do I automate evidence-driven code reviews for changed files?▼

Run static analysis and diff review against changed files to generate structured findings with severity, line numbers, and precise fixes. This standardized workflow ensures consistent, evidence-based quality checks per change.

What is the best way to prevent code reviews from flagging intentional architectural choices?▼

Load non-negotiable decisions from pipeline.yml to prevent code reviews from flagging intentional architectural choices. This configuration guides the review process, filtering out non-actionable decisions and ensuring only relevant issues are surfaced.

How does static analysis integrate with diff review for quality assurance?▼

Static analysis integrates with diff review by scoping SAST checks and context-aware reviews specifically to changed files. This combination applies configurable criteria across a defined workflow, producing evidence-based findings for downstream QA remediation.

Can I use pipeline.yml to configure static analysis rules for security and code quality?▼

Yes, you can use pipeline.yml to configure static analysis rules for security and code quality. The review workflow applies these non-negotiable rules to changed files, generating structured findings with rule IDs and actionable fixes.

What structured reporting format does the code review output for downstream QA?▼

The code review outputs a structured reporting contract for downstream QA containing severity, file path, line number, rule ID, and precise fixes. This format standardizes per-change quality reviews and ensures evidence-based findings.

Do I need dependencies to run SAST checks and diff analysis on feature branches?▼

No dependencies are required to run SAST checks and diff analysis on feature branches. The review workflow operates independently, applying configurable criteria to code diffs and generating actionable findings without external tool dependencies.