repo-cleanup-1-build-artifacts
Sub-skill of repo-cleanup: 1. Build Artifacts (+5).
Best use case
repo-cleanup-1-build-artifacts is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of repo-cleanup: 1. Build Artifacts (+5).
Teams using repo-cleanup-1-build-artifacts should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/1-build-artifacts/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How repo-cleanup-1-build-artifacts Compares
| Feature / Agent | repo-cleanup-1-build-artifacts | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of repo-cleanup: 1. Build Artifacts (+5).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 1. Build Artifacts (+5) ## 1. Build Artifacts Files generated during build/install processes that should not be tracked. | Pattern | Description | Location | |---------|-------------|----------| | `*.egg-info/` | Python package metadata | `src/*/` | | `__pycache__/` | Python bytecode cache | Throughout | | `.pytest_cache/` | Pytest cache | Root and test dirs | | `build/` | Build output directory | Root | | `dist/` | Distribution packages | Root | | `*.pyc` | Compiled Python files | Throughout | *See sub-skills for full details.* ## 2. Log Files Generated log files that accumulate during development and testing. | Pattern | Description | |---------|-------------| | `*.log` | General log files | | `*LogFile.txt` | OrcaFlex log files | | `*.log.*` | Rotated log files | | `debug.log` | Debug output | **Cleanup commands:** *See sub-skills for full details.* ## 3. Temp Files Temporary files created during processing or editing. | Pattern | Description | |---------|-------------| | `*.tmp` | Temporary files | | `.temp/` | Temp directories | | `cache/` | Cache directories | | `*.bak` | Backup files | | `*.swp` | Vim swap files | | `*~` | Editor backup files | *See sub-skills for full details.* ## 4. Coverage Reports Test coverage artifacts that can be regenerated. | Pattern | Description | |---------|-------------| | `htmlcov/` | HTML coverage reports | | `.coverage` | Coverage data file | | `.coverage.*` | Parallel coverage data | | `coverage.xml` | XML coverage report | **Cleanup commands:** ```bash # Remove coverage artifacts rm -rf htmlcov/ rm -f .coverage .coverage.* coverage.xml ``` ## 5. IDE Artifacts Editor and IDE generated files. | Pattern | Description | |---------|-------------| | `.idea/` | PyCharm/IntelliJ | | `.vscode/` | VS Code (keep settings.json) | | `*.code-workspace` | VS Code workspaces | | `.spyproject/` | Spyder IDE | **Note:** Some IDE settings may be intentionally tracked. Check `.gitignore` first. ## 6. Benchmark Artifacts Benchmark directories often contain mixed content that needs separation. | Pattern | Description | Action | |---------|-------------|--------| | `benchmarks/reports/` | Timestamped HTML reports | Add to .gitignore | | `benchmarks/results/` | Timestamped CSV/JSON | Add to .gitignore | | `benchmarks/legacy_projects/` | Reference test data | Move to tests/fixtures/ | | `benchmarks/*.py` | Benchmark scripts | Keep tracked | **Cleanup commands:** *See sub-skills for full details.*
Related Skills
interactive-report-generator
Generate interactive HTML reports with Plotly visualizations from data analysis results. Supports dashboards, charts, and professional styling.
data-validation-reporter
Generate interactive validation reports with quality scoring, missing data analysis, and type checking. Combines Pandas validation, Plotly visualization, and YAML configuration for comprehensive data quality reporting.
repo-ecosystem-hygiene
Interpret the daily read-only repo ecosystem hygiene audit and route remediation through approved workflows.
mnt-analysis-cleanup
Survey, classify, and clean up `/mnt/local-analysis/` (or any sibling-to-workspace-hub directory holding orphan worktrees, codex-burn artifacts, agent log accumulations, and outer-clone duplicates) without losing useful code/work. Surfaces a tiered approval menu rather than baking decisions; defers all destructive ops until user confirms.
orcaflex-reporting-fixture-proof-pattern
Build and extend fixture-backed OrcaFlex reporting proof paths in digitalmodel using stable metadata baselines, normalized HTML snapshots, and reusable reporting test helpers.
pre-completion-cleanup-audit
Audit and dispose of session residue (orphan files, scratch dirs, sibling-repo state, locks, trash-stages) BEFORE claiming a task complete. Required gate before any agent says "all done", "task complete", or hands work back to user/orchestrator.
repo-sync
Smart repository synchronization across workspace-hub ecosystem — diagnoses and fixes pull failures (detached HEAD, diverged branches, uncommitted changes)
repo-structure
Canonical source layout, test mirroring, root cleanliness, gitignore, docs classification, and committed artifact rules for all workspace-hub tier-1 repos. Consult before creating directories or files in any submodule.
repo-portfolio-steering
Generate a one-page portfolio steering report for workspace-hub. Use when the user invokes /repo-portfolio-steering, asks about harness vs engineering balance, wants a portfolio health check, or asks which repos to fund next. Reports on portfolio steering, GTM readiness, and provider activity balance.
repo-mission-portfolio-audit
Audit the workspace-hub repo portfolio to extract each repo's mission, identify documentation gaps, and prioritize a plan/approval sequence with explicit LLM-wiki weighting for future issue triage.
mixed-ops-vs-repo-fix-plan-boundary
Plan mixed operational-vs-repo remediation issues by proving live-state classification first, then only proposing code changes for confirmed repo-owned failure paths.
repo-separation-for-sensitive-data
Architecture pattern for splitting confidential data and reusable algorithms across repos