skills.rest
Elad73
Elad73COMMUNITY
Explore all skills by this author →
GitHub

cleanup

Audit stale project artifacts and generate a confirmation-gated cleanup plan.

Updated Jun 22, 2026
Search Tags:#git#cache management#cleanup#safe deletion#artifact audit#session files
One-click install
npx skills add https://github.com/Elad73/agentic-base-layer --skill cleanup-elad73
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cleanup
Source: https://github.com/Elad73/agentic-base-layer/tree/main/global/skills/cleanup
Command: npx skills add https://github.com/Elad73/agentic-base-layer --skill cleanup-elad73

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you identify and remove stale project artifacts without accidentally touching active work, secrets, or other sensitive files.

Core Features & Use Cases

  • Artifact Audit: Reviews merged git branches, stale session handoff files, and temporary build or test outputs.
  • Safe Cleanup Workflow: Uses a report-first, confirm-then-delete process so the user explicitly chooses what gets removed.
  • Use Case: When a repository feels cluttered after a long development session, this Skill can prepare a safe cleanup plan for caches, debug screenshots, and obsolete branches.

Quick Start

Use the cleanup skill to audit stale artifacts in this repository and ask me to prepare a safe cleanup plan for the selected category.

Frequently Asked Questions about cleanup

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

FAQPage Schema
How do I safely clean up stale git branches and temp files without deleting active work?▼

An audit-first cleanup workflow identifies stale git branches and temporary files, then requires explicit confirmation before deleting artifacts, ensuring your active branch and sensitive files remain untouched.

What is the best way to prune cluttered git repositories after a long development session?▼

The best way to prune cluttered repositories is running a conservative audit that targets stale session files, temp directories, and caches, followed by a user-confirmed deletion plan to safely remove the identified clutter.

Can I dry-run repository cleanup before removing merged branches and debug screenshots?▼

Yes, you can dry-run repository cleanup to review merged branches and debug screenshots before removal. The process uses dry-run checks and confirmation gates to let you verify artifacts before any deletion occurs.

Does safe project cleanup protect sensitive files and secrets during artifact pruning?▼

Safe project cleanup protects sensitive files and secrets by applying branch safety rules and conservative deletion commands that never target protected files, ensuring only stale artifacts like caches and temp outputs are pruned.

When should I perform an artifact audit on my project's temporary build outputs and caches?▼

You should perform an artifact audit when repositories feel cluttered after long sessions or during pre-archive maintenance, identifying stale build outputs, session files, and caches for a safe, confirmed cleanup plan.

Related Skills

Explore More Software Engineering Skills→
OpenSourcePharmaFoundationOpenSourcePharmaFoundation
4

branch-cleanup

Identify stale or merged Git branches and delete them after user approval.

Community
Intermediate
Atrium-HermesAtrium-Hermes

Janitor

Delete stale .notify-*, .pending-notify-temp, and .outputs artifacts by TTL.

Community
Intermediate
dtsongdtsong
1

Git Delete Branch

Delete local and remote Git branches with merged and force checks.

Community
Intermediate
leadgenjayleadgenjay
11

cleanup

Audit project workspaces and remediate security, temp, git, dependency, dead code, build, and quality issues.

Community
Advanced