Harden repository quality and CLI safety - #7
Merged
Conversation
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
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.
Summary
Why
The repository had a strong baseline, but interrupted state writes could corrupt
run-state.json, directory artifact validation could follow symlinks, numeric overflow could serialize invalid state, and branch protection relied on only one structural check. Validation dependencies and GitHub Actions references were also not fully reproducible.Impact
The v1 workflow contract and dependency-free runtime remain unchanged. Invalid or unsafe local states now fail earlier with explicit CLI errors, and repository checks are deterministic and easier to enforce.
Validation
npm run checkuvx --from skills-ref==0.1.1 agentskills validate <skill-path>gh skill publish --dry-runuvx --from actionlint-py actionlintuvx zizmor --pedantic .git diff --checkTwo symlink tests are skipped locally on Windows because symlink creation returns
EPERM; the GitHub Actions Linux and macOS jobs exercise those paths.