Skip to content

ci: add plugin template validation workflow (changeset-based)#188

Draft
jatinkrmalik wants to merge 1 commit into
mainfrom
ci/add-template-validation
Draft

ci: add plugin template validation workflow (changeset-based)#188
jatinkrmalik wants to merge 1 commit into
mainfrom
ci/add-template-validation

Conversation

@jatinkrmalik

Copy link
Copy Markdown
Collaborator

What

Adds a lightweight GitHub Actions workflow (.github/workflows/ci.yml) that runs the existing scripts/validate-template.mjs validator on PRs and pushes to main.

The validator checks the plugin / marketplace manifests, SKILL.md (and other component) frontmatter, and that referenced paths exist. It uses only Node built-ins — no npm install, no dependencies.

Why

This repo currently has no committed CI. A small validation check is far more useful here than heavyweight SAST: it catches broken manifests and malformed skill frontmatter before merge, which is the realistic failure mode for a skills/plugin repo.

Changeset behaviour

Per the request to not run on basic doc changes, the workflow uses paths-ignore to skip prose-only edits:

  • README.md, CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md, LICENSE, CODEOWNERS
  • images/**, assets/**, **/*.svg

Note: skill Markdown (SKILL.md and other component frontmatter) is intentionally not ignored, because validate-template.mjs validates that frontmatter — so skill edits still trigger the check.

Notes

  • Verified locally: node scripts/validate-template.mjsValidation passed. (exit 0).
  • The CLA check is unaffected — it's an external Atlassian commit status, not a workflow.
  • Does not touch CodeQL. Converting CodeQL to changeset-based (path-filtered) requires switching it from "Default setup" to "Advanced setup" in repo Settings, which a committed file alone can't do; happy to follow up with that separately.

Adds a GitHub Actions workflow that runs scripts/validate-template.mjs on
pull requests and pushes to main. The script validates the plugin/marketplace
manifests, skill frontmatter, and referenced paths (no external dependencies).

Uses paths-ignore to skip prose-only documentation changes (README,
CONTRIBUTING, images, etc.) so the check does not run on basic doc edits.
Skill Markdown is intentionally not ignored since its frontmatter is validated.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant