repo-cleanup-progress-tracking-commands
About
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.
Quick Install
Claude Code
Recommendednpx skills add vamseeachanta/workspace-hub -a claude-code/plugin add https://github.com/vamseeachanta/workspace-hubgit clone https://github.com/vamseeachanta/workspace-hub.git ~/.claude/skills/repo-cleanup-progress-tracking-commandsCopy and paste this command in Claude Code to install this skill
GitHub Repository
Related Skills
legal-sanity-review
OtherThis 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
OtherThe 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-structure-section-updates
OtherThis skill handles repository structure documentation updates after cleanup operations. It automatically updates directory trees, removes references to deleted folders, and documents architectural changes like `.claude/` folders and consolidated scripts. Use it to maintain accurate structure sections in README files following repository reorganization.
brainstorming-best-practices
OtherThis Claude Skill provides structured best practices for effective brainstorming sessions, focusing on user-centered approaches like starting with needs and validating options. It offers clear "Do" and "Don't" guidelines to maintain productive collaboration and avoid premature solutions. Developers should use this reference skill when facilitating brainstorming to ensure thorough understanding and documented decisions.
