ci: enforce skills-only diffs on PRs#62
Open
kevarifin14 wants to merge 2 commits intomainfrom
Open
Conversation
Blocks any PR that adds or modifies files outside the allowed set: - `*.md` (SKILL.md, references, docs) - `.claude-plugin/marketplace.json` Prevents helper scripts, SDK code, and other non-instructional files from landing. Matches the no-code rule in CONTRIBUTING.md. Maintainers can bypass via the `allow-infra-change` label when legitimately updating CI, scripts, LICENSE, etc.
christopherdro
previously approved these changes
Apr 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a CI check that fails any PR touching files outside the allowed set:
Why
We just closed a PR (#57/#61, zyfai-yield) that shipped `scripts/*.js` helper files. CONTRIBUTING.md already forbids code in skills, but nothing enforced it — reviewers have to catch it manually, and I missed it on approval. This makes the rule machine-enforced.
Escape hatch
Adding the `allow-infra-change` label to a PR bypasses the check. Use this when legitimately updating:
The label is controlled by maintainers, so contributors can't bypass without sign-off.
Test plan
Note: this PR itself touches `.github/workflows/` so I'll need the `allow-infra-change` label applied (or merge it before the workflow is live on the base).