Code quality checks

Dude's comprehensive code quality definitions and pre-commit hooks for WordPress projects.

Features

• Pre-commit hooks with comprehensive code quality checks
• Automatic context detection (standalone theme vs dudestack project)
• Build system detection (Parcel or Gulp)
• PHP CodeSniffer validation
• Stylelint for SCSS files
• WordPress version checks (dudestack mode)
• Dependency validation for Composer and npm
• Merge conflict and scissor mark detection
• Commit message validation with Linear integration
• AI attribution rejection in commit messages

Installation

npm install @digitoimistodude/code-quality-checks husky --save-dev

Initialize husky:

npx husky init

Setup

Create wrapper scripts in your project's .husky/ directory that reference the package hooks.

.husky/pre-commit

node_modules/@digitoimistodude/code-quality-checks/.husky/pre-commit

.husky/commit-msg

node_modules/@digitoimistodude/code-quality-checks/.husky/commit-msg "$1"

Make them executable:

chmod +x .husky/pre-commit .husky/commit-msg

Context detection

The hooks automatically detect whether they're running in:

• dudestack project: Has content/themes/ directory and composer.json
• Standalone theme: Everything else

dudestack mode checks

• WordPress version in composer.json
• Composer dependencies
• CHANGELOG.md format and freshness
• Theme style.css validation
• Multi-theme dependency checks
• Root stylelintrc should not exist

Standalone mode checks

• Basic file requirements (.nvmrc, phpcs.xml)
• Build system config (Parcel: .parcelrc or Gulp: gulpfile.js)
• npm dependencies
• Stylelint config in current directory
• PHP syntax validation
• SCSS linting

Commit message rules

Every commit message is validated in the commit-msg hook.

Linear reference

The message must carry a task ID and a magic word, for example Fix navigation bug, Ref: DEV-123.

No AI attribution

The commit is rejected if the message carries attribution to an AI tool. This covers Co-Authored-By trailers naming an assistant or model, generated-with lines such as Generated with Claude Code, AI vendor footer links and AI session URLs. The check runs before the merge-commit escape hatch, so a merge commit cannot carry attribution either.

Co-Authored-By trailers for real people are untouched. Use assistants as much as you like, just do not sign the history with them.

When a commit is rejected, amend it rather than bypassing the hook:

git commit --amend

See the organisation contributing rules for the policy this enforces.

Configuration

Create .husky/pre-commit-config in your project to override defaults:

# Directories to exclude
EXCLUDE_DIRS=".husky|node_modules|vendor|.git|uploads|cache"

# Files to exclude (glob patterns)
EXCLUDE_FILES="*.min.js|*.min.css|*.map|*.lock|*.log"

# File extensions to exclude
EXCLUDE_EXTENSIONS=".jpg|.jpeg|.png|.gif|.svg|.ico|.pdf"

# Check only changed files (true) or entire codebase (false)
CHECK_CHANGED_ONLY=true

Requirements

• Node.js >= 18.0.0
• PHP >= 8.1
• Composer (for dudestack projects)
• husky >= 9.1.7

Updating

Simply update the package to get the latest hooks:

npm update @digitoimistodude/code-quality-checks

No need to re-copy files - your wrapper scripts always use the latest version from node_modules.