agentleFS
jinhuang712jinhuang712/claude-code-broom/skills/sweep/SKILL.md

sweep

Skill0 starsChanged yesterdayMITView on GitHub

Sweep code with broom on request - format, lint and type-check a scope the user describes in their own words (uncommitted changes, what's staged, the last few commits, this branch, some folders, or the whole repo) and report what is left. Use for /broom:sweep, or when asked to clean up, format, lint or check code.

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use incident, pickup and 10 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.
  • JkudjoSkill

    incident

    Production incident response — structured triage, hypothesis tree, safe remediation, incident record

    Also in 3 projects that use this

  • HermeticOrmusSkill

    pickup

    Read a HANDOFF.md and restore session context. The entry ritual -- the opposite of /handoff. Use at the start of a new session after a handoff, machine switch, or context clear.

    Also in 3 projects that use this

  • asterkinSkill

    adr

    Create Architecture Decision Records (ADRs) following project standards. Guides template usage, process, and best practices for documenting architecturally significant decisions.

    Also in 4 projects that use this

  • anombyte93Skill

    discover

    Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

    Also in 3 projects that use this

  • GitHubSkill

    refactor

    Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

    Also in 5 projects that use this

  • MicrosoftSkill

    diagnose

    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

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every scope formats its files except --all, which only reports: formatting a whole repo makes a large diff.

    line 22
  2. Very specific:

    Run broom sweep --all --fix only after the user confirms they want every file reformatted.

    line 23
  3. Distinctive:

    If it reports missing tools, offer /broom:setup.

    line 27

“Common” is measured: kept by at least 6 in 10 of the 17 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Turn the request ($ARGUMENTS, or the conversation) into a broom sweep command and run it from the repo root.

The user saysCommand
nothing, "my changes", "what I'm working on"broom sweep
"what I staged", "what's about to be committed"broom sweep --staged
"the last commit", "the last 3 commits"broom sweep --base HEAD~1, broom sweep --base HEAD~3
"since <commit or tag>"broom sweep --base <rev>
"this branch", "my PR"broom sweep --base "$(git merge-base HEAD <default branch>)"
"the whole repo", "everything"broom sweep --all
"src/api", "these files"add the paths to any of the above
"just check", "don't change anything"add --check
"including the ones we accepted"add --include-known
  • The default branch is usually main; check with git symbolic-ref refs/remotes/origin/HEAD when unsure.
  • Every scope formats its files except --all, which only reports: formatting a whole repo makes a large diff. Run broom sweep --all --fix only after the user confirms they want every file reformatted.
  • Lint findings count only on the lines in scope (with --all, every line); compile and type errors count anywhere. Issues accepted earlier stay hidden, and the output says how many.
  • Relay the report grouped as printed. Fix the findings only if the user asked for fixes.
  • If it reports missing tools, offer /broom:setup.
  • For code smells ranked across the repo and a cleanup worst first, use /broom:clean instead.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.