sweeper

Reconciles a repository's technical-debt tracker and lands updates as a pull request.

1|Updated Aug 14, 2026
One-click install
npx skills add https://github.com/zhiyuan-zhang0206/Ava --skill sweeper-zhiyuan-zhang0206
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sweeper
Source: https://github.com/zhiyuan-zhang0206/Ava/tree/main/ava_builtins/skills/sweeper
Command: npx skills add https://github.com/zhiyuan-zhang0206/Ava --skill sweeper-zhiyuan-zhang0206

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a repository's technical-debt tracker accurate is tedious: entries go stale, resolved debt lingers, and new debt goes unrecorded. This Skill automates one full reconcile pass so the tracker always reflects what debt is actually open right now. ## Core Features & Use Cases - Re-verification of open entries: Re-checks every open debt item against current evidence and deletes entries whose debt is resolved, while never touching wontfix items. - Debt discovery and dedup: Runs the project-local debt-class scans, fingerprints findings, and adds only genuinely new items that meet a strict evidence bar. - PR-based landing: Advances the tracker watermark to the current HEAD SHA and opens a pull request via gh, never pushing to main; no-op runs open no PR. - Use Case: A team maintains a living debt tracker doc in their repo. On a schedule, an agent runs this sweep to close resolved items, record newly detected debt, and open a chore PR summarizing added and resolved counts. ## Quick Start Ask the agent to sweep this repository's technical-debt tracker and open a PR with any updates.

Frequently Asked Questions about sweeper

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

FAQPage Schema
How do I automate technical debt tracking in a repository?▼

Run a reconcile pass that re-verifies each open tracker entry against current evidence, deletes resolved items, runs the project-local debt-class scans to discover new debt, and opens a pull request with the updated tracker. The sweep never pushes directly to main.

How does the sweeper decide which debt findings to record?▼

It applies a strict evidence bar: only strong, concrete findings are recorded, and anything that would be labeled maybe is dropped. Reasoned findings must name specific files and symbols plus one line explaining why they are a smell.

What happens if a repository has no project-local sweeper skill?▼

The sweep stops and reports that the repo has not been set up for sweeping. The repo-agnostic procedure does not invent debt classes; the project-local skill must supply the tracker file path and the concrete scans to run.

Does the sweeper ever modify wontfix entries or push to main?▼

No. Wontfix entries are skipped entirely and never re-evaluated or re-added. All tracker changes land exclusively through a pull request created with gh pr create; the procedure never pushes to main.

What happens when a sweep finds no changes to the tracker?▼

If nothing was added and nothing resolved, the run is reported as a no-op and no pull request is opened. A PR is only created when the tracker content actually changed.