chore(pre-commit): validate plugins on pre-push
## Why `claude plugin validate --strict` catches structural issues in plugin manifests that `check-manifests.sh` does not cover (e.g. schema violations, unrecognised fields). Running it at pre-push ensures all plugins in `plugins/*/` stay valid before reaching the remote. Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -52,6 +52,15 @@ repos:
|
|||||||
pass_filenames: false
|
pass_filenames: false
|
||||||
always_run: true
|
always_run: true
|
||||||
|
|
||||||
|
- id: validate-plugins
|
||||||
|
name: Validate plugins
|
||||||
|
description: Run claude plugin validate --strict on every plugin directory
|
||||||
|
entry: bash -c 'for d in plugins/*/; do claude plugin validate --strict "$d" || exit 1; done'
|
||||||
|
language: system
|
||||||
|
stages: [pre-push]
|
||||||
|
pass_filenames: false
|
||||||
|
always_run: true
|
||||||
|
|
||||||
- id: skill-frontmatter
|
- id: skill-frontmatter
|
||||||
stages: ['pre-commit']
|
stages: ['pre-commit']
|
||||||
name: SKILL.md frontmatter validation
|
name: SKILL.md frontmatter validation
|
||||||
|
|||||||
Reference in New Issue
Block a user