hidden-folder-audit
О программе
Этот навык проводит аудит и консолидацию скрытых папок в репозиториях, выявляя дубликаты, нерабочие директории и возможности для объединения таких папок, как .agent-os/, .ai/ и .claude/. Он полезен, когда в репозиториях со временем накопилось несколько конфигурационных директорий для ИИ/агентов или содержатся битые символьные ссылки. Инструмент помогает очистить и стандартизировать структуру скрытых папок.
Быстрая установка
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/hidden-folder-auditСкопируйте и вставьте эту команду в Claude Code для установки этого навыка
Документация
Hidden Folder Audit
When to Use
- Repository has accumulated multiple hidden folders over time
- Multiple AI/agent configuration directories exist (
.agent-os/,.ai/,.claude/) - Symlinks point to non-existent targets
- Unclear which configuration is authoritative
- Preparing for repository restructure or cleanup
- After inheriting or forking a repository
- Before establishing new folder standards
Related Skills
- repo-cleanup - General repository cleanup
- module-based-refactor - For source code restructuring
- session-start-routine - Session initialization
References
- Git ls-files documentation: https://git-scm.com/docs/git-ls-files
- Git check-ignore documentation: https://git-scm.com/docs/git-check-ignore
- Symbolic links in Git: https://git-scm.com/book/en/v2/Git-Internals-Git-References
Version History
- 1.2.0 (2026-01-20): Added Related Directory Patterns section
- Added benchmarks/ entry to reference table (SPLIT action)
- Added Related Directory Patterns section for non-hidden directories
- Added specs/archive/ as standard location for completed plans
- Added benchmarks/ separation pattern (fixtures vs generated outputs)
- Updated verification commands for new patterns
- 1.1.0 (2026-01-20): Updated reference table and added verification commands
- Updated Common Hidden Folders Reference table with verified recommendations
- Added .drcode/ as DELETE (confirmed legacy AI config)
- Added .slash-commands/ as CONSOLIDATE to .claude/docs/commands/
- Added .git-commands/ as CONSOLIDATE to scripts/git/
- Added .benchmarks/ as DELETE (usually empty)
- Added .githooks/ as KEEP (standard location)
- Added Verification Commands section with:
- Verify Hidden Folder State commands
- Verify Consolidation Targets commands
- Verify Git Status commands
- Final State Checklist script
- Added Notes column to reference table for additional context
- 1.0.0 (2025-01-20): Initial release based on digitalmodel repository hidden folder audit session
Sub-Skills
Sub-Skills
GitHub репозиторий
Похожие навыки
legal-sanity-review
ДругоеThis mandatory workflow scans code for legal risks like client names or proprietary references before cross-review. It blocks the review cycle if violations are found, requiring fixes first. Use it as a pre-gate for PR creation, code porting, or any cross-review trigger.
brainstorming
ДругоеThe brainstorming skill transforms initial ideas into detailed specifications through iterative questioning and collaborative dialogue. It helps developers explore design options, evaluate trade-offs, and create shared understanding before implementation. This prevents rework by systematically refining concepts into actionable plans.
repo-cleanup-progress-tracking-commands
ДругоеThis sub-skill provides shell commands for tracking file counts during repository cleanup operations, specifically for hidden folders like `.claude` and `.agent-os`. It includes verification scripts to ensure no files are lost after merging changes. Use it when consolidating or reorganizing project directories to monitor progress and validate results.
brainstorming-metrics
ДругоеThis skill provides structured metrics for evaluating brainstorming sessions, including targets for questions per design, validation rates, and stakeholder alignment. It helps developers measure brainstorming effectiveness and implementation quality. Use it to establish clear success criteria and track rework during project planning phases.