pr-review

Automating PR review involves running a validation script to verify SKILL.md frontmatter, directory-name alignment, and license presence. This workflow catches policy violations early and reduces manual effort for new skill submissions.

A two-phase code review workflow applies automated validation checks first, followed by manual soft-quality guideline reviews. This ensures structural metadata compliance before human reviewers assess the actual quality of the submission.

Validating YAML frontmatter requires checking the SKILL.md file against expected metadata fields. The validation script ensures frontmatter validity, name-directory alignment, and required metadata presence to maintain repository standards.

Yes, the PR review workflow includes secret scanning across all skill files. It detects hardcoded keys and tokens during the automated validation phase to prevent sensitive credentials from merging into the repository.

Yes, you can use the validation script to audit existing skills. It checks SKILL.md frontmatter, directory-name consistency, and license presence, applying the same compliance rules used for new pull request submissions.

Automated PR compliance checks are limited to structural validation like frontmatter format and secret scanning. They cannot evaluate subjective quality, so a manual soft-quality review phase is required to fully assess documented guidelines.