sweep

Detects code duplication against a checklist and returns verified findings with runnable verifier commands.

4|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/laicluse/agent-fieldkit --skill sweep-laicluse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sweep
Source: https://github.com/laicluse/agent-fieldkit/tree/main/.agents/plugins/generated/drydry/skills/sweep
Command: npx skills add https://github.com/laicluse/agent-fieldkit --skill sweep-laicluse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Duplication audits often produce vague, unverifiable findings that teams cannot act on. This Skill runs an independent detection pass over a defined scope against a named checklist and returns only findings backed by a runnable verifier command and a concrete drift hypothesis. ## Core Features & Use Cases - Checklist-driven detection: Scans a directory, glob, or file list against 6-10 named duplication patterns, capping findings per pattern to avoid noise. - Verifier-burden enforcement: Every finding must include a runnable command (grep, rg, find) that re-confirms the pair; findings whose verifiers fail are dropped. - Drift-hypothesis discipline: Each finding states the concrete consequence of continued drift, rejecting vague claims like "would be cleaner to share". - Use Case: During a drydry audit of a large repository, the orchestrator routes to this Skill to walk the scope, downsample oversized file sets by language, and return structured markdown findings the orchestrator assembles into the audit artefact. ## Quick Start Ask the agent to run the drydry audit pipeline over a target directory so the sweep detection pass returns verified duplication findings.

Frequently Asked Questions about sweep

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

FAQPage Schema
How do I detect code duplication across a repository?▼

Run a detection pass over a defined scope against a checklist of duplication patterns. Each finding pairs two file locations with a runnable verifier command (grep, rg, or find) that re-confirms the match without the detector in the loop.

How to verify duplication findings automatically?▼

Require every finding to include a verifier command, then execute each command in a separate context after detection. Drop findings whose command exits non-zero, produces no output, or fails to reference both paired files.

Can this sweep skill be invoked directly by users?▼

No, it is an internal detection pass, not user-invocable. The operator runs the drydry orchestrator command, which routes to this skill with a scope and checklist as inputs.

What happens when the scope is too large to scan?▼

When the file count exceeds the max_files cap (default 2000), the skill downsamples by language, keeping primary source files and dropping tests and fixtures unless the checklist names them. The downsample decision is logged for verification.

Why are some duplication findings dropped from the report?▼

Findings are dropped when they lack a runnable verifier command, when the drift hypothesis is vague (like "feels redundant" without a concrete consequence), or when the verifier command fails during re-execution. Off-list patterns go to a separate checklist-gaps section.