cleanup-build-artifacts

Solid

Removes transient build artifacts this task produced in the ironlint repo before declaring work done. Use at the end of any task that ran `cargo build --release`, `cargo mutants`, `cargo llvm-cov`, generated a one-off binary, wrote a scratch file like `pr.diff` or an ad-hoc tarball, or any other throwaway output. Do NOT use to wipe the actively-iterating `target/` directory.

Web & Frontend 16 stars 2 forks Updated 1 weeks ago Apache-2.0

Install

View on GitHub

Quality Score: 81/100

Stars 20%
41
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Cleanup Build Artifacts Sweep up the transient artifacts *this task* produced so the working tree and disk stay clean. Implements the AGENTS.md / AGENTS.md rule: "Clean up build artifacts you produced once the task is done." ## Scope **In scope** — artifacts created during this task: - Release binaries built for one-off verification (`target/release/<bin>`) - `cargo mutants` output (`mutants.out/`, `mutants.out.old/`) - `cargo llvm-cov` reports (`target/llvm-cov-target/`, generated `lcov.info` / HTML report dirs) - Scratch files at the repo root: `pr.diff`, `*.diff`, ad-hoc `*.tar`/`*.tar.gz`, throwaway `*.log`, `scratch_*`, `tmp_*` - One-off binaries built outside `target/` (e.g. via `--out-dir`) - Temporary fixture dirs created for an investigation that aren't checked in **Out of scope — DO NOT TOUCH:** - The persistent `target/` debug tree being actively iterated on (`cargo build`, `cargo test` incremental output). Leave it. - Anything tracked by git that's modified (M) or staged — those are real work. - `.ironlint/` runtime state unless the task explicitly created it for a one-off check. - Pre-existing files in the working tree the task didn't author. If unsure whether something is yours, leave it. ## Instructions ### Step 1: Enumerate what this task produced Before cleaning, list candidates. Run these in parallel: ```bash # Untracked files that appeared during the task git status --short --untracked-files=normal # Release binaries (likely candidates if you ra...

Details

Author
ironlint
Repository
ironlint/ironlint
Created
2 months ago
Last Updated
1 weeks ago
Language
Rust
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

cleanup-unused-files

Aggressively clean disk space by removing caches, build artifacts, temporary folders, tool state, and other reproducible local junk from repos and developer machines. Use when the user asks to free space, nuke caches, wipe local build output, remove stale tool directories, clear package-manager caches, reset local developer state, or do a broad cleanup of bulky unused files.

36 Updated today
OpenCoven
Code & Development Listed

cleanup

Tear down a finished task's transient resources — kill the dev server / e2e / Playwright processes it started, remove the git worktree, prune stale preview deployments (keeping the last N), and note the cleanup on the parent issue. Use once a task's PR is merged (or abandoned) and you want the workspace and running resources reclaimed. Recommend-only — never auto-invoked by another skill; the user starts it. Triggers on "정리해줘", "리소스 정리", "worktree 제거", "cleanup", "teardown", "clean up the task", "e2e 종료".

1 Updated today
gitgitWi
AI & Automation Listed

clean

Audit an arbitrary directory tree for orphaned, temporary, stale-lock, failed-write, partial-download, and empty leftover artifacts; classify evidence into confidence tiers; and optionally remove exact validated paths after explicit per-tier approval. Read-only by default and manual-only. Use when: 'audit this directory', 'find orphaned files', 'what junk can I clean up', 'reclaim disk space', 'find temp or lock leftovers', 'clean up my home directory'. Skip when: repository cache/build cleanup belongs to repo-hygiene, a product has its own prune/GC command, or the target is an OS-managed root.

4 Updated today
melodic-software