clean-artifacts-and-git-history

Removes build artifacts and temporary files while enforcing atomic commits and git hygiene.

Updated May 16, 2026
One-click install
npx skills add https://github.com/alimtvnetwork/img-pdf-v2 --skill clean-artifacts-and-git-history-alimtvnetwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-artifacts-and-git-history
Source: https://github.com/alimtvnetwork/img-pdf-v2/tree/main/.agents/skills/clean-artifacts-and-git-history
Command: npx skills add https://github.com/alimtvnetwork/img-pdf-v2 --skill clean-artifacts-and-git-history-alimtvnetwork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repositories accumulate pycache folders, build outputs, test logs, and coverage dumps that pollute commits and waste CI storage, and this Skill automates their safe removal while enforcing disciplined git practices. ## Core Features & Use Cases - Artifact Cleanup: Removes pycache, build artifacts, test logs, and coverage dumps via the artifact-remover script. - GitHub Actions Storage Management: Purges obsolete remote CI artifacts when GitHub Actions storage approaches quota, using a dedicated purge script or workflow. - Git Hygiene Enforcement: Ensures .gitignore covers new intermediate files, requires consolidated atomic commits, and mandates immediate pushes after committing. - Use Case: Before wrapping up a development session, run this Skill to clean generated files, verify .gitignore coverage, commit all changes as one atomic unit, and push to the remote branch. ## Quick Start Clean all build artifacts and temporary files from this repository, then commit everything as a single atomic commit and push it to the remote branch.

Frequently Asked Questions about clean-artifacts-and-git-history

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

FAQPage Schema
How do I clean build artifacts and pycache from a repository?

Run the artifact-remover script at 03-ai-scripts/19-artifact-remover.py to delete pycache folders, build outputs, test logs, and coverage dumps. The Skill also verifies that .gitignore rules cover any newly introduced intermediate files.

How to free up GitHub Actions artifact storage?

Purge obsolete remote artifacts by running 03-ai-scripts/34-purge-github-actions-artifacts.py with the --repo flag and your repository slug, or trigger the purge-actions-artifacts.yml workflow. The Skill enforces zero upload-artifact usage in CI workflows to prevent quota issues.

Does this cleanup process run full builds or tests?

No, routine cleanup explicitly avoids full builds such as npm run build or go build, and does not run the local CI runner. This keeps cleanup fast and focused on artifact removal and git hygiene only.

Why commit all changes as one atomic commit instead of small commits?

The Skill enforces consolidated atomic commits so related modified files and plans stay together as a single unit, avoiding fragmented piecemeal commits of one or two files. Every commit is pushed immediately to the remote branch afterward.

When should I not use automated artifact cleanup?

Avoid running cleanup when generated files are still needed for debugging active test failures or when build outputs must be preserved for deployment. Verify .gitignore coverage first so important intermediates are not accidentally committed or deleted.