Draft: expand claude-lint path verification plan - #82
Draft
randlee wants to merge 1 commit into
Draft
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
This draft PR extends the
claude-lintplan so path verification is an explicit part of the skill design, not just an implied review behavior.Added to the plan
packages/sc-claude-lint/scripts/verify-path-references.pylint-path-resolution.pyWhy
The skill needs a mechanical way to prove that referenced paths resolve correctly across:
.claude/...installs./...and../...references.claude/...paths back to package source artifacts~/.claude/...Without supplemental scripts, this part of the linting surface stays too manual and too easy to regress.
Notes