agentleFS
diriendirien/yet-another-agent-harness/.claude/skills/scout/SKILL.md

scout

Skill19 starsChanged 8 months agoMITView on GitHub

Scout Rule — identify the top 3 highest-impact improvement opportunities in files you're already touching. Analyzes entire file content, not just changed lines. Focuses on pre-existing code quality, not PR bugs. Use when preparing a PR, during code review, or after completing a feature.

47 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use expand, explain and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • andrewclark88Skill

    expand

    Expand a project's scope by updating its foundation documents. Reads existing north-star.md (or north-star-<project>.md), architecture.md, and roadmap.md, understands the codebase state, then interviews the user about the expansion. Updates foundation docs and roadmap so design can consume them in the next phase. Use when adding a major capability, new subsystem, or architectural shift — not for small one-offs (use feature for those).

    Also in 3 projects that use this

  • sunnyclinches44Skill

    explain

    Explains code using real-world analogies and ASCII diagrams

    Also in 5 projects that use this

  • WordPressSkill

    blueprint

    Use when the deliverable is WordPress Playground Blueprint JSON or a Blueprint bundle, including creating, editing, reviewing, validating schema keys, choosing steps/resources, and debugging Blueprint files. For only running or sharing a Playground environment, use wp-playground.

    Also in 3 projects that use this

  • AWSSkill

    issue

    Implement a GitHub issue end-to-end — branch, code, test, docs, and commit.

    Also in 3 projects that use this

  • bradtraversySkill

    feature

    Manage current feature workflow - start, review, explain or complete

    Also in 3 projects that use this

  • HK-hubSkill

    distill

    Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 43 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If git is not installed or the working directory is not a git repository, stop and report the issue.

    line 30
  2. Distinctive:

    If all sources return empty, report that there are no changed files to analyze.

    line 50
  3. Distinctive:

    If the user specifies a target branch to analyze, detect the base branch the same way as the default mode, then diff:

    line 55
  4. Distinctive:

    If given an explicit list of file paths rather than a branch name, use those directly without running git diff.

    line 66
  5. Distinctive:

    Read the full content of each changed file, not just diff hunks.

    line 71
  6. Distinctive:

    Look for improvements in the entire file.

    line 72
  7. Distinctive:

    If no improvement opportunities are found, report:

    line 151

“Common” is measured: kept by at least 6 in 10 of the 43 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Copyright 2025-2026 Richard Shade. Licensed under Apache-2.0. --><!-- SPDX-License-Identifier: Apache-2.0 -->

Scout Rule

"Leave the code better than you found it."

Identify the top 3 highest-impact, lowest-risk improvement opportunities in files touched by a diff. Reads entire file content, not just changed lines. Focuses on pre-existing code quality — things the next developer will thank you for fixing.

Prerequisite check

git --version 2>/dev/null && git rev-parse --is-inside-work-tree 2>/dev/null

If git is not installed or the working directory is not a git repository, stop and report the issue. Do not proceed.

Detect changed files

Determine which files to analyze based on input.

Default — working tree vs base branch

# Detect base branch
BASE_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null \
  | sed 's@^refs/remotes/origin/@@' || echo "main")

# Combine committed + uncommitted + staged changes vs base
{ git diff --name-only ${BASE_BRANCH}...HEAD 2>/dev/null; \
  git diff --name-only; \
  git diff --name-only --cached; } | sort -u

If all sources return empty, report that there are no changed files to analyze.

Specific branch

If the user specifies a target branch to analyze, detect the base branch the same way as the default mode, then diff:

BASE_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null \
  | sed 's@^refs/remotes/origin/@@' || echo "main")
git diff --name-only ${BASE_BRANCH}...${BRANCH}

Specific files

If given an explicit list of file paths rather than a branch name, use those directly without running git diff.

Scope

Read the full content of each changed file, not just diff hunks. Look for improvements in the entire file.

Do not:

  • Find bugs in PR changes (that's a code reviewer's job)
  • Suggest architectural redesigns
  • Flag style preferences not established in the codebase
  • Propose changes requiring new dependencies

Categories

dead-code

Unused functions, variables, imports, or types. Commented-out code blocks. Unreachable branches. Stale TODO/FIXME comments referencing completed work.

naming

Misleading names that don't match current behavior (code evolved, name didn't). Inconsistent patterns within the same file (e.g., getUserID vs fetchUserId). Single-letter variables in non-trivial scope (beyond simple loop counters). Abbreviations that hurt readability when the full word is short.

magic-values

Hardcoded numbers or strings that should be named constants. Repeated literal values that represent the same concept. Timeout/limit values embedded in logic without explanation.

deprecated-patterns

Old APIs when newer alternatives exist in the same codebase. Patterns that the project has moved away from (check other recent files for the modern approach). Legacy error handling when the project now uses a different convention.

simplification

Overly complex logic that can be expressed more directly. Unnecessary indirection (wrapper functions that add no value). Redundant nil/error checks where the invariant is already guaranteed. Nested conditionals that can be flattened with early returns.

Scoring

Score each opportunity on two dimensions (1-5 each):

  • Impact: How much does fixing this help the next developer?
    • 5 = Prevents real confusion or bugs
    • 3 = Noticeable improvement to readability
    • 1 = Minor polish
  • Low-Risk: How safe is this change?
    • 5 = Pure cleanup, zero behavior change possible
    • 3 = Safe but touches logic paths
    • 1 = Could change behavior if not careful

Composite score = Impact × Low-Risk. Return only the top 3.

Output format

Present a summary table followed by per-suggestion details:

#File:LineCategoryDescriptionEffortScore
1locationcategorydescriptioneffortI×R=S
2locationcategorydescriptioneffortI×R=S
3locationcategorydescriptioneffortI×R=S

For each suggestion, include:

  • Category and Effort (trivial / small / medium)
  • Why this matters — one sentence explaining value to the next developer
  • Suggested change — concrete code snippet or diff showing the improvement

If no improvement opportunities are found, report:

No significant improvement opportunities found. The touched files are in good shape.

Anti-patterns — do not suggest

  • Refactoring entire files or modules
  • Changing public API signatures
  • Style preferences not established in the codebase
  • Anything requiring new dependencies or architectural decisions
  • Changes that would touch more than ~20 lines
  • Issues a linter would catch

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.