scout

Identify the top 3 high-impact code-quality improvements in touched files using Git diffs.

3|Updated Mar 18, 2026

Search Tags:#refactor #improvement #code-quality #code-review #pull-request #diff-analysis #scout

Ready to run

npx skills add https://github.com/rshade/agent-skills --skill scout-rshade

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scout
Source: https://github.com/rshade/agent-skills/tree/main/skills/scout
Command: npx skills add https://github.com/rshade/agent-skills --skill scout-rshade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify top 3 high-impact opportunities in files you are already touching, enabling faster code-quality improvements without exhaustive manual reviews.

Core Features & Use Cases

Scans entire touched files, not just diffs, to surface meaningful quality enhancements.
Prioritizes changes by impact and risk, helping you focus PR cleanups and code reviews.
Use Case: during a PR review, after implementing a feature, or when stabilizing a codebase with legacy hints.

Quick Start

Run a scan on your current working tree to surface the top 3 improvement opportunities.

Frequently Asked Questions about scout

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

FAQPage Schema

How do I identify high-impact code improvements during a pull request review?▼

To identify high-impact code improvements during a pull request, scan the entire content of touched files rather than just the diff to surface and prioritize the top 3 quality enhancements by impact and risk.

How does diff analysis find pre-existing code quality issues in touched files?▼

Diff analysis finds pre-existing code quality issues by using Git to detect changed files, then analyzing the entire file content to surface meaningful refactor opportunities beyond the immediate changed lines.

What is the best way to guide targeted cleanup after implementing a feature?▼

The best way to guide targeted cleanup after implementing a feature is to run a scan on your working tree to surface the top 3 high-impact code-quality improvements in the files you already touched.

Do I need Git to detect diffs for code review and refactor analysis?▼

Yes, you need Git to detect diffs because the code review and refactor analysis relies on identifying files you have touched during development to scope the quality improvement scan.

Can I use this approach to stabilize a codebase with legacy code hints?▼

Yes, you can use this approach to stabilize a codebase with legacy hints by focusing cleanup efforts on pre-existing code within files you are already modifying, ensuring faster quality improvements.

Why does the code review scan analyze entire files instead of just changed lines?▼

The code review scan analyzes entire files instead of just changed lines to surface meaningful pre-existing quality enhancements that would be missed if only evaluating the immediate diff context.