skills.rest
MaiconGambini
MaiconGambiniCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

harness-cleanup-scanner

Scan repositories and report cleanup candidates without deleting files.

Updated Jul 29, 2026
Search Tags:#cleanup#code hygiene#report#repository scan#debug files#untracked files#stale todos
One-click install
npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-cleanup-scanner-maicongambini
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-cleanup-scanner
Source: https://github.com/MaiconGambini/opencode-harness-guide/tree/main/skills/harness-cleanup-scanner
Command: npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-cleanup-scanner-maicongambini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repositories accumulate debug files, temporary reports, stale TODOs, and orphan artifacts over time, and deleting them blindly risks losing important work. This Skill scans the project and produces a risk-assessed cleanup report so you can review candidates before anything is removed. ## Core Features & Use Cases - Read-only scanning: Detects debug files, scratch scripts, temporary reports, stale TODO/FIXME notes, orphan harness artifacts, large untracked files, and old handoffs without modifying anything. - Structured risk report: Outputs a markdown table with category, path, evidence, risk level, and recommended action for each finding. - Approval-gated cleanup: Separates safe cleanup from risky cleanup and requires explicit approval before any deletion. - Use Case: Before a release, run a scan to surface leftover debug scripts and duplicate progress files, review the risk table, then approve only the safe removals. ## Quick Start Scan this repository for cleanup candidates and report debug files, stale TODOs, and large untracked files with risk levels, without deleting anything.

Frequently Asked Questions about harness-cleanup-scanner

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

FAQPage Schema
How do I find leftover debug and temp files in a repository?▼

Run a cleanup scan that checks for debug files, scratch scripts, temporary reports, and generated artifacts. The scan reports each candidate with its exact path, evidence, and risk level without deleting anything.

How to detect stale TODO and FIXME comments in code?▼

The scan flags TODO and FIXME notes that have no owner and appear stale. Each finding is listed in the report with its path and a recommended action so you can triage or remove them.

Does the cleanup scan delete files automatically?▼

No. The scan is read-only by default and never modifies or deletes files during analysis. Cleanup actions require explicit approval, and safe cleanup is separated from risky cleanup in the report.

Can it find large untracked files before committing?▼

Yes. One of the scan checks targets large untracked files that may bloat a repository if committed. These are reported with their paths so you can add them to ignore rules or remove them.

What are the limitations of a report-only cleanup scanner?▼

It does not perform any remediation itself, so a human must review the risk table and approve actions. It also relies on heuristics for staleness, so some flagged items may still be intentionally kept.

Related Skills

Explore More Software Engineering Skills→
broomvabroomva
25

harness-engineering-playbook

Bootstrap OpenAI Harness Engineering practices with a Typer-based CLI.

Community
Advanced
djnsty23djnsty23
2

clean

Automate cleanup of temporary and legacy artifacts in code projects.

Community
Intermediate
forcedotcomforcedotcom
11

fix-lint-errors

Remove unused variables and imports from JavaScript and TypeScript files.

Official
Basic
BPSAIBPSAI

finishing-branches

Run pre-merge checks, scan for secrets, and prepare pull requests on feature branches.

Official
Intermediate