repo-cleanup-1-build-artifacts
について
このスキルは、バージョン管理で追跡すべきではないビルド成果物や生成ファイルを特定し、クリーンアップを支援します。特にPython開発の出力物、バイトコードキャッシュ、配布用ディレクトリ、ログファイルなどを対象としています。一時的なビルドファイルや開発ログを削除してクリーンなリポジトリを維持する必要がある場合に、このサブスキルをご利用ください。
クイックインストール
Claude Code
推奨npx skills add vamseeachanta/workspace-hub/plugin add https://github.com/vamseeachanta/workspace-hubgit clone https://github.com/vamseeachanta/workspace-hub.git ~/.claude/skills/repo-cleanup-1-build-artifactsこのコマンドをClaude Codeにコピー＆ペーストしてスキルをインストールします
ドキュメント
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:
# 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.
GitHub リポジトリ
関連スキル
content-collections
メタThis skill provides a production-tested setup for Content Collections, a TypeScript-first tool that transforms Markdown/MDX files into type-safe data collections with Zod validation. Use it when building blogs, documentation sites, or content-heavy Vite + React applications to ensure type safety and automatic content validation. It covers everything from Vite plugin configuration and MDX compilation to deployment optimization and schema validation.
polymarket
メタThis skill enables developers to build applications with the Polymarket prediction markets platform, including API integration for trading and market data. It also provides real-time data streaming via WebSocket to monitor live trades and market activity. Use it for implementing trading strategies or creating tools that process live market updates.
creating-opencode-plugins
メタThis skill helps developers create OpenCode plugins that hook into 25+ event types like commands, files, and LSP operations. It provides the plugin structure, event API specifications, and implementation patterns for JavaScript/TypeScript modules. Use it when you need to intercept, monitor, or extend the OpenCode AI assistant's lifecycle with custom event-driven logic.
cloudflare-turnstile
メタThis skill provides comprehensive guidance for implementing Cloudflare Turnstile as a CAPTCHA-alternative bot protection system. It covers integration for forms, login pages, API endpoints, and frameworks like React/Next.js/Hono, while handling invisible challenges that maintain user experience. Use it when migrating from reCAPTCHA, debugging error codes, or implementing token validation and E2E tests.