repo-janitor

Remove build and scan artifacts before commits via pre-commit hooks.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/oioio-space/unpixel --skill repo-janitor-oioio-space
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-janitor
Source: https://github.com/oioio-space/unpixel/tree/main/.claude/skills/repo-janitor
Command: npx skills add https://github.com/oioio-space/unpixel --skill repo-janitor-oioio-space

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that unnecessary build and scan artifacts are not committed to the repository, maintaining a clean and organized codebase.

Core Features & Use Cases

  • Automated Cleanup: Removes build and scan artifacts like dist/, coverage.out, and sbom.cdx.json before commits.
  • Pre-commit Hook Integration: Works with pre-commit hooks to prevent commits with unwanted artifacts.
  • Manual Check: Provides a manual checklist for AI review before committing to ensure no artifacts are being committed.

Quick Start

Run mise run clean before committing to remove artifacts and prevent them from being committed.

Frequently Asked Questions about repo-janitor

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

FAQPage Schema
How do I prevent build artifacts from being committed to my repository?

Preventing build artifacts from being committed involves integrating pre-commit hooks to automatically remove known untracked files like dist/ and coverage.out before they enter the staging area.

What is the best way to remove scan artifacts before a git commit?

The best way to remove scan artifacts before a git commit is to run a dedicated cleanup script. This removes files like sbom.cdx.json and blocks the commit if any staged file is a scan artifact.

Does the pre-commit hook integration block commits containing coverage.out files?

Yes, the pre-commit hook integration blocks commits containing coverage.out files. It automatically removes known untracked artifacts and prevents the commit if any staged file is a build or scan artifact.

How do I manually check for sbom.cdx.json or dist/ files before committing?

You can manually check for sbom.cdx.json or dist/ files by using a manual checklist for AI review before committing. This ensures no build or scan artifacts are being committed to the repository.

Can I run repository maintenance tasks without setting up pre-commit hooks?

Yes, you can run repository maintenance tasks without setting up pre-commit hooks by executing the manual clean command. This removes known untracked artifacts before you stage your files.

Why are untracked build artifacts still showing up in my staged files?

Untracked build artifacts show up in staged files if they were added before running cleanup. You must run the clean command before committing to remove artifacts and prevent them from being committed.