plugin-validator: pre-commit output is too noisy

[Jamie-BitFlight]

Copied from Jamie-BitFlight/claude_skills#130

Story

As a developer using Claude Code skills, I want to plugin-validator: pre-commit output is too noisy so that the tooling becomes more capable and complete.

Description

Running prek --all-files produces pages of plugin-validator output — every file in the repo gets validated, and pre-existing warnings/errors (broken links, SK006 complexity, missing trigger phrases) for files unrelated to the current change drown out actionable information. The validator needs a review of its pre-commit integration to reduce noise.

Details

Source: prek --all-files run during session 2026-02-15
Added: 2026-02-15
Description: Running prek --all-files produces pages of plugin-validator output — every file in the repo gets validated, and pre-existing warnings/errors (broken links, SK006 complexity, missing trigger phrases) for files unrelated to the current change drown out actionable information. The validator needs a review of its pre-commit integration to reduce noise.

Observed symptoms:

• Full prek --all-files run produces hundreds of lines of validator output
• Pre-existing LK001 (broken links), SK006 (complexity warnings), SK005 (missing triggers) reported on every run
• FM003 (no frontmatter) fires on template files (commands/development/templates/*.md) that are not components — they're templates meant to be copied and filled in, not commands/skills/agents
• Difficult to find actual issues in changed files among the noise

Related: "plugin-validator UX and coverage gaps" sub-issues below, "Resolve plugin-validator pre-existing errors to make CI gate blocking" backlog item
File: plugins/plugin-creator/scripts/plugin_validator.py, .pre-commit-config.yaml

Acceptance Criteria

• Work matches description
• Plan or implementation complete

Context

• Source: prek --all-files run during session 2026-02-15
• Priority: P1
• Added: 2026-02-15
• Research questions: None