hygiene

Validate staged changes against pre-commit hygiene checks.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Nithwin/shadowcode --skill hygiene-nithwin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hygiene
Source: https://github.com/Nithwin/shadowcode/tree/main/.github/skills/hygiene
Command: npx skills add https://github.com/Nithwin/shadowcode --skill hygiene-nithwin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ShadowCode hygiene checks run as a git pre-commit hook. Commits will be rejected if hygiene fails.

Core Features & Use Cases

  • Pre-commit hygiene checks catch Unicode issues, improper quotes, missing copyright headers, indentation problems, and formatting errors.
  • ESLint and Stylelint are applied to enforce code quality across TypeScript and CSS files.
  • Use Case: Before declaring work complete or merging into main, run hygiene to ensure all files conform to project standards.

Quick Start

Run the pre-commit hygiene check before committing your changes.

Frequently Asked Questions about hygiene

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

FAQPage Schema
How do I enforce pre-commit code quality checks for ESLint and Stylelint?

Pre-commit hygiene checks validate staged files against formatting, indentation, quote rules, and copyright headers using ESLint and Stylelint. Commits are automatically rejected if any hygiene violations are detected in the staged changes.

What does a pre-commit hook check to prevent Unicode and formatting issues?

A pre-commit hook checks staged files to detect Unicode characters, improper quotes, missing copyright headers, indentation problems, and formatting errors. It applies these validation rules across the entire codebase to ensure deterministic code hygiene before any commit is finalized.

Do I need npm to run pre-commit hygiene checks on staged files?

Yes, you need npm installed to run the pre-commit hygiene checks on staged files. The hygiene script requires npm to execute deterministic validation against staged changes before allowing a commit to proceed in the repository.

What's the best way to ensure TypeScript and CSS files conform to project standards before merging?

To ensure TypeScript and CSS files conform to project standards before merging, run a pre-commit hygiene check that applies ESLint and Stylelint validation. This prevents incomplete or non-compliant work from being committed into the main branch.

Why does my git commit fail when hygiene checks detect formatting errors?

Your git commit fails because the pre-commit hook detects hygiene violations such as formatting errors or missing copyright headers. The hook rejects the commit to enforce clean code standards, requiring you to fix the identified issues before trying to commit again.