find

Repository context. Gather first

Collect these with individual Bash calls, one command per call, never combined into a single invocation:

• Current branch, git branch --show-current
• Recent commits, git log --oneline -15
• Working tree status (empty = clean), git status --porcelain | head -10
• Shallow repository, git rev-parse --is-shallow-repository

The pipe is the bound and belongs in the command. A read-time cap ("read only the first 10 entries") bounds nothing: the Bash tool returns the command's complete output into context before there is anything to decide about.

Treat a failure (not a repository, git unavailable) as an unknown value and carry on. A worktree-isolated session refuses a compound command that contains git, which is why each call above stays on its own. The dated record for that refusal, and for the pre-compute composition that makes it bite, is the source-control plugin's worktree/reference/gather-block.md, "The pre-compute block runs as one shell invocation".

Variables

Arguments: $ARGUMENTS

Purpose

This skill answers "what should we improve here, and how do we know?", the second half of that question is its identity. Review evaluates a diff; planning designs already-chosen work; the specialized finders each hunt one lens. This skill forms its own cross-dimension judgment about what is worth improving in a target: code, product behavior, process surfaces, operational setup, and grounds every proposal in cited evidence, so ranking reflects measurement, not taste. It discovers and deliberates only: execution always flows through the repo's normal pipeline (interview → discovery → planning → implementation → verification).

Prompt interpretation

Parse $ARGUMENTS and the invoking prompt for four independent narrowings; each defaults open:

• Target scope. Bare invocation scans the whole repo across every dimension below. A targeted ask, "improve ", "improve ", "improve ", narrows the scan: map the named feature/path/concept to its concrete surfaces (files, workflows, config, ops touchpoints) before gathering evidence, and gather evidence for those surfaces only. A concept with no resolvable surface is itself a finding (likely instrument-first, below).
• Size band. --small / --medium / --large (or equivalent prose: "quick wins only", "big swings") restricts candidates to that size band. Default: all sizes, ranked together.
• Repo as parameter. One repo per invocation. An explicit repo path in the arguments makes that checkout the target; otherwise the current repo is. When the target is not the session's working directory, resolve its root once (git -C <repo-path> rev-parse --show-toplevel) and anchor EVERY probe to it. git -C <root> for every git command here and in the context/ recipes, and file reads under that root, so the evidence never silently comes from the invoking repo. The branch/log calls above describe the session's cwd, not the target; re-run them with -C <root> in that case. Fleet-wide sweeps are out of scope. Compose with repo-fleet-hygiene externally, one invocation per repo.
• Mode. Interactive is the default. Unattended is entered ONLY when the caller declares it (see Unattended mode), never inferred from context.