review-git-workdir_skill

Overview

This skill reviews the current Git working directory and produces a focused code-review-style summary of issues, surprises, and cleanup opportunities. It runs a quick inspection of changed files and highlights debug artifacts, commented-out code, unused imports, and other potential problems to address before committing or publishing. The goal is to catch human slips and noisy changes that reduce code quality or leak implementation details.

How this skill works

The skill starts by running git status to list modified, added, and deleted files in the working tree. It inspects diffs and file contents to identify common problems (leftover console/log statements, commented-out blocks, dead code, stray temporary files, and generated-artifact noise). It ignores known generated artifacts such as protobuf outputs and any files with a .gensum extension. It then outputs a prioritized list of findings with actionable recommendations.

When to use it

• Before committing or opening a pull request to catch accidental debug or dead code.
• When preparing a release or publishing to ensure no debug logs or temporary artifacts are included.
• During code review to provide an automated pre-check of the working tree.
• After merging branches to spot leftover conflict markers or leftover test scaffolding.
• When cleaning up or refactoring to identify unused exports or imports.

Best practices

• Run this check locally before commits and CI to reduce noisy diffs and review churn.
• Add project-specific ignore rules for generated files to avoid false positives.
• Treat found debug statements and commented-out production code as high-priority fixes.
• Resolve unused imports and dead code early to keep bundle size and complexity down.
• Include automated linting and pre-commit hooks to catch recurring issues automatically.

Example use cases

• Detect accidental console.log or debugger left in a feature branch before opening a PR.
• Find commented-out experimental code that should be removed or moved to a feature flag.
• Spot stray .gensum files or generated artifacts that should be excluded from commits.
• Identify unused module exports or imports introduced during refactors.
• Catch merge conflict markers or temporary test scaffolding leftover after merges.