workspace-hygiene

Audit git workspace changes before commits and pull requests.

Updated May 7, 2026
One-click install
npx skills add https://github.com/prototypdigital/claude-marketplace --skill workspace-hygiene-prototypdigital
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workspace-hygiene
Source: https://github.com/prototypdigital/claude-marketplace/tree/main/llm/skills/workspace-hygiene
Command: npx skills add https://github.com/prototypdigital/claude-marketplace --skill workspace-hygiene-prototypdigital

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the review of workspace state before commits or pull requests, ensuring clean, focused changes and preventing unintended side effects.

Core Features & Use Cases

  • On-Demand Audit: Conduct a quick review of workspace changes to confirm only expected files are modified.
  • Commit Focus: Ensures commits are atomic and focused, with suggestions for splitting mixed-commit scenarios.
  • Temporary Artifacts Removal: Cleans up temporary files and debug statements, maintaining a clean codebase.
  • Secrets Verification: Checks for sensitive information in staged changes to prevent data leaks.
  • PR History Cleanliness: Suggests squashing or reordering commits for a clean pull request history.
  • Use Case: Before opening a pull request, use this Skill to verify that only the intended files have changed, commits are focused, and no secrets are exposed.

Quick Start

Run the workspace-hygiene skill to audit your workspace before committing or opening a pull request.

Frequently Asked Questions about workspace-hygiene

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

FAQPage Schema
How do I audit my workspace state before opening a pull request?

To audit your workspace state before a pull request, run the workspace-hygiene skill to verify only intended files are modified, ensuring clean commits and preventing unintended side effects. It requires git and Python for analysis and reporting.

How do I check staged changes for secrets to prevent data leaks?

To check staged changes for secrets, use the workspace-hygiene skill to verify sensitive information in your commits. This prevents data leaks by identifying exposed secrets before you push to a remote repository.

What is the best way to ensure my git commits are atomic and focused?

Ensuring atomic and focused git commits is achieved by using the workspace-hygiene skill, which reviews your workspace state and provides suggestions for splitting mixed-commit scenarios into clean, targeted changes.

Can I clean up temporary files and debug statements before committing code?

You can clean up temporary files and debug statements before committing by running a workspace audit. The workspace-hygiene skill automates this cleanup, maintaining a clean codebase and preventing unintended changes.

How do I clean up a messy pull request history before merging?

To clean up a messy pull request history, the workspace-hygiene skill suggests squashing or reordering commits. This ensures a clean PR history and focused changes before the final merge into the main branch.

Do I need Python and git to analyze my workspace for unintended changes?

Yes, you need both git and Python installed to use the workspace-hygiene skill. These dependencies are required for the script to analyze your repository state and generate reports on unintended file modifications.