yet-another-agent-harness: Skill for Claude Code

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