agentleFS
Sign inStart free
jrittelmeyerjrittelmeyer/ai-dev-kit/.claude/skills/tidy/SKILL.md

tidy

Skill1 starsChanged 27 days agoMITView on GitHub

Local dev-machine hygiene — prune the project's unbounded build/engine cache to its size cap, report disk + cache size, then surface (not auto-run) the judgment-required cleanups (orphaned dev processes, stale test data, dangling container images). Use at a checkpoint boundary, when disk is low, or when the build cache "is huge" / "clean up the machine".

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use map, architect and 3 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.
  • AWSSkill

    map

    Map verified service capabilities against customer-provided control framework and threat model. Produces mapping-results.json, controls-catalog.md, and framework-mapping.md. Supports pluggable frameworks: CCMv4, NIST 800-53, CIS Benchmarks, ISO 27001, etc. Split into 4 focused sub-skills for better accuracy; this skill orchestrates them.

    Also in 3 projects that use this

  • Harut8Skill

    architect

    Also in 3 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    verify

    End-to-end app testing pipeline for browser-based web apps on cloud browsers via Azure Playwright Workspaces: verify the live app, author tests for working flows, heal failing tests, then re-run with video and produce one consolidated report. Three phases (app verification, test authoring, test healing) plus a scoped final sanity run; each phase emits a sub-report. Use when asked to "verify my app", "make sure my app works and has good test coverage", "do a full QA pass", "add tests where I'm missing coverage", "fix failing tests and add new ones", "smoke test before deploy", "QA my deployment", or any combined verify-and-test ask. Requires Azure CLI (`az login`) and a Playwright Workspace resource ID — bootstraps configs on first invocation. Browser-based web apps with Playwright only — not for unit/API tests, native mobile/desktop, load/perf, or full accessibility audits.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

tidy

Reclaim local disk and keep the working machine healthy. Most stacks have at least one unbounded grower — a build or engine cache with no native TTL or size cap that quietly accumulates gigabytes. This skill's core job is pruning that cache; the rest it surfaces rather than runs, because those need judgment.

Adapter: .claude/ai-dev-kit.config.json (cache, hygiene); a missing field → ask or skip that section. Per-stack cache locations, growth patterns, and platform commands: references/hygiene-recipes.md.

1. Prune the build cache (safe, automatic)

  • Report first: run the adapter's cache.size command.
  • Prune to the cap: run cache.prune (typically deletes oldest entries until under a ceiling while keeping recent builds for cache hits; prefer a --dry-run preview when the command offers one).
  • Report reclaimed space and current disk free (platform commands in the recipes file).

This same prune often runs automatically at two points (so it rarely has much to do here): the checkpoint cadence during active build sessions, and any pre-push backstop the repo wires. This skill is the on-demand / deeper pass.

2. Surface the judgment-required cleanups (do NOT auto-run)

Report each with its reclaim potential and the exact command, then let the user pick:

  • Orphaned dev processes on the adapter's hygiene.devPorts (or the stack's equivalent: dev servers, watchers, emulators, editor daemons) — a stopped background task can leave a process holding a port or lock. Tree-kill by PID; keep containers and the browser.
  • Stale test data matching the adapter's hygiene.e2eUserPattern (or the project's seeded-data convention) — accumulated throwaway rows eventually break pagination- and count-dependent tests. A mass DELETE always needs explicit user OK; keep everything that doesn't match the pattern.
  • Dangling container images / build layers — CI image work leaves large layers; prune commands are in the recipes file. Keep the running containers named in hygiene.keepContainers.
  • Stack-specific growers the recipes file lists for this project type (engine import caches, dependency caches, old toolchain versions) — surface only what the repo actually uses.

3. Report

One short summary: disk free before → after, cache size before → after, and which surfaced items (if any) the user chose to run. Don't silently perform step-2 actions.

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.

Check your setup, free