sweep
Skill4 starsChanged 29 days agoMITView on GitHub
Scan codebase for debug artifacts and code quality issues; optionally auto-fix safe patterns. Use when: before committing, during PR review, or periodic codebase cleanup. Not for: structural code improvement — use /refactor; security-specific scanning — use /scan. Keywords: sweep, debug cleanup, console.log, debugger, TODO, ts-any, code quality.
21 other projects use a version of this.
Adopted by
Most recently taken up by
- ronniepinnell/caspertheir own version, first seen Nov 8, 2026
- jisuzzzz/haechitheir own version, first seen Nov 8, 2026
- AsiaOstrich/universal-dev-standardsword for word, first seen Nov 4, 2026
- venhdev/skillstheir own version, first seen Nov 1, 2026
- YSAA1/harness-workflowtheir own version, first seen Oct 30, 2026
- MH221B/skillstheir own version, first seen Oct 24, 2026
Used with
Projects with it also use diagnose, triage and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkilldiagnose
Use to systematically diagnose why scenarios fail — identifies root causes by analyzing agent traces, codebase, and behavioral patterns
Also in 4 projects that use this
Google CloudSkilltriage
Gather context on a change or bug and plan the implementation.
Also in 4 projects that use this
GoogleSkillcodebase-design
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Also in 3 projects that use this
Other versions21 projects use a version of this.
Word for word · 1
- AsiaOstrich/universal-dev-standards★ 84100% same
Edited · 0
None found.
Wrote their own version · 20
- fallow-rs/fallow★ 5.3ksame name
- simota/agent-skills★ 96same name
- optave/ops-codegraph-tool★ 94same name
- enapt/SwarmLLM★ 82same name
- iamneilroberts/claude-skills★ 26same name
- jisuzzzz/haechi★ 17same name
- leek/agent-skills★ 5same name
- YSAA1/harness-workflow★ 3same name
- drewdrewthis/claude-skills★ 2same name
- MH221B/skills★ 2same name
10 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository55 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ac-coverageSkill
- adrSkill
- ai-collaboration-standardsSkill
- ai-friendly-architectureSkill
- ai-instruction-standardsSkill
- api-designSkill
- atddSkill
- auditSkill
- bddSkill
- brainstormSkill
- changelogSkill
- checkinSkill
- ci-cdSkill
- code-reviewSkill
- commitSkill
- contract-testSkill
- databaseSkill
- deploySkill
- methodologySkill
- dev-workflowSkill
- docgenSkill
- documentation-guideSkill
- durableSkill
- e2eSkill
- error-code-guideSkill
- git-workflow-guideSkill
- incidentSkill
- journey-test-assistantSkill
- knowledge-graphSkill
- logging-guideSkill
- metricsSkill
- migrateSkill
- observabilitySkill
- orchestrateSkill
- planSkill
- prSkill
- discoverSkill
- project-structure-guideSkill
- pushSkill
- refactorSkill
- releaseSkill
- requirementSkill
- retrospectiveSkill
- reverseSkill
- runbookSkill
- securitySkill
- scanSkill
- skill-builderSkill
- sloSkill
- spec-deriveSkill
- sddSkill
- tddSkill
- coverageSkill
- testing-guideSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 48
Use Glob tool to find all source files under the target path.
- Very specific: line 49
Default excludes: node_modules/, dist/, .git/, *.min.js, coverage/.
- Very specific: line 69
If --fix flag is set AND total fixable findings exceed 20:
- Distinctive: line 70
Pause and require explicit user confirmation: before applying fixes. Show the list of files that will be modified.
- Distinctive: line 78
Use Edit tool to apply changes file by file.
- Very specific: line 82
Write findings to .uds/sweep-report.json:
- Very specific: line 120
After /sweep completes, suggest:
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Sweep Assistant | 掃碼助手
Language: English | 繁體中文
Scan the codebase for debug artifacts, code quality issues, and technical debt markers. Optionally auto-fix safe patterns (console.log, debugger statements).
Scan Patterns | 掃描模式
| Pattern ID | Label | Auto-fixable | Description |
console-log | console.log / console.debug / console.trace | ✅ Yes | Debug output left in production code |
debugger | debugger statement | ✅ Yes | Debugger breakpoints left in code |
todo-fixme | TODO / FIXME / HACK / XXX | ❌ Report only | Technical debt markers |
ts-any | TypeScript any type | ❌ Report only | Type safety violations |
Usage | 使用方式
/sweep # Scan current directory, report findings
/sweep --fix # Scan and auto-fix fixable patterns
/sweep --report # Scan and save report to .uds/sweep-report.json
/sweep --path src/ # Scan specific directory
/sweep --exclude "**/*.test.ts" # Exclude patterns (glob)Workflow | 執行工作流程
Step 1: Discover Files
Use Glob tool to find all source files under the target path.
Default excludes: node_modules/, dist/, .git/, *.min.js, coverage/.
Step 2: Scan Each Pattern
For each pattern, use Grep to find matches across all files.
Collect findings: { file, line, column, pattern_id, label, fixable, content }.
Step 3: Report Findings
Output a structured summary:
📊 Sweep Results
─────────────────────────────────────
console-log: 12 findings (auto-fixable)
debugger: 2 findings (auto-fixable)
todo-fixme: 28 findings (report only)
ts-any: 5 findings (report only)
─────────────────────────────────────
Total: 47 findings | Fixable: 14Step 4: HITL Gate (if --fix and findings > 20)
If --fix flag is set AND total fixable findings exceed 20:
Pause and require explicit user confirmation before applying fixes.
Show the list of files that will be modified.
Step 5: Apply Fixes (if --fix confirmed)
For each fixable finding:
console-log: Remove the line if it contains only the console statementdebugger: Remove the line if it contains only the debugger statement
Use Edit tool to apply changes file by file. Report: "Fixed N findings in M files."
Step 6: Save Report (if --report)
Write findings to .uds/sweep-report.json:
{
"timestamp": "<ISO8601>",
"total_findings": 47,
"fixable": 14,
"fixed": 14,
"findings_by_pattern": { "console-log": 12, "debugger": 2, "todo-fixme": 28, "ts-any": 5 },
"files_modified": ["src/auth.ts", "src/utils.ts"]
}Configuration | 設定
Configure via uds.project.yaml:
sweep:
default_path: "src/"
exclude_patterns:
- "**/*.test.ts"
- "**/*.spec.ts"
- "**/fixtures/**"
hitl_threshold: 20 # Require confirmation if fixable findings exceed this
patterns:
enabled:
- console-log
- debugger
- todo-fixme
- ts-anyNext Steps Guidance | 下一步引導
After /sweep completes, suggest:
- Run
/checkinto verify overall code quality before committing- Run
/code-reviewto review the cleaned-up changes- Run
/committo commit the fixes
Related Standards | 相關標準
- Checkin Standards — Pre-commit quality gates
- Code Review — Code review assistant
- Testing Guide — Testing standards
Version History | 版本歷程
| Version | Date | Changes |
| 1.0.0 | 2026-04-28 | Initial release — XSPEC-097 Phase 1 (從上游遷移) |
License | 授權
This skill is released under MIT License and CC BY 4.0.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

