scan-new-code

Analyze PR diffs to detect large functions, missing tests, and high complexity.

Updated Aug 27, 2026

Search Tags:#testing #code-quality #static-analysis #analyze #ci #diff-scan #pr-diff

Ready to run

npx skills add https://github.com/TrevorPLam/agency --skill scan-new-code

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scan-new-code
Source: https://github.com/TrevorPLam/agency/tree/main/.windsurf/skills/scan-new-code
Command: npx skills add https://github.com/TrevorPLam/agency --skill scan-new-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes PR diffs to flag potential issues in newly added code before merge.

Core Features & Use Cases

Detects large functions in changed files.
Flags missing tests and high complexity in PR diffs.
Integrates with PR reviews and CI pipelines to enforce a code-quality baseline.

Quick Start

Review the latest pull request diff and run the scan-new-code workflow to surface potential quality issues before merging.

Frequently Asked Questions about scan-new-code

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

FAQPage Schema

How do I scan PR diffs for code quality issues before merging?▼

To scan PR diffs for code quality issues, you analyze newly added or changed files to detect large functions, missing tests, and high complexity. This surfaces potential regressions in code reviews before merging to ensure a baseline quality.

What is static analysis for pull request diffs?▼

Static analysis for pull request diffs evaluates only the newly added or changed code to flag potential issues. It targets large functions, missing tests, and high complexity to preempt regressions and maintain a quality baseline during reviews.

Can I integrate diff scanning into CI pipelines to enforce code quality?▼

Yes, you can integrate diff scanning into CI pipelines to enforce a code-quality baseline. It analyzes PR diffs during CI checks to detect large functions, missing tests, and high complexity in changed code before merges.

What's the best way to detect missing tests in changed code?▼

The best way to detect missing tests in changed code is running a PR diff scan. It specifically flags missing tests alongside large functions and high complexity in newly added files, reporting findings in a structured format for reviews.

Does PR diff static analysis flag large functions and high complexity?▼

Yes, PR diff static analysis flags large functions and high complexity. By targeting newly added or changed files during code reviews, it surfaces these specific code-quality issues in a structured, automatable format to preempt regressions.