research: name every flagged referenced file, not just divergent ones - #60
Merged
Merged
Conversation
The first step-2 scan (60 skills, seed 20260816) returned a divergence set of zero with three referenced files flagged SUSPICIOUS. Both facts matter, but the report only printed the first, so the three were invisible: which skills, which paths, which rules, all unrecoverable without re-running. A file whose SKILL.md already flagged is not concealment -- documentation and code agreeing is the honest case, and it is precisely why those three are outside the divergence set. That is a reason to label them, not to drop them. A flag you cannot see is a flag you cannot check. Also lists the named-but-unreachable paths by skill. Thirteen of 120 paths 404'd; they are already excluded from the clean count, but a reader has no way to tell which skills carry that unknown. Raises the job timeout to 120 minutes so a 300-skill scan (~900 registry fetches at 0.55s, plus rule-engine time per file) fits. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DNoTXU8k3pfSBzR7aJubqL
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.
What the first scan showed
Run 34654103313 (60 skills, seed 20260816):
An empty divergence set is a real result and it argues against the hypothesis that motivated this tooling: the unread surface is confirmed large, but in this draw nothing is hiding in it.
Why this change
Three files were flagged and the report named none of them. They fall outside the divergence set because their skill's
SKILL.mdwas itself non-clean — documentation and code agreeing, which is the honest case, and the opposite of concealment. That is a reason to label them, not to drop them. As written, the only way to recover which skills, which paths, and which rules was to re-run the scan.Two additions:
Timeout goes to 120 minutes so a 300-skill scan fits: roughly 900 registry fetches at the 0.55s pacing, plus rule-engine time on every fetched file.
Not changed
No detection logic, no thresholds, no extraction rules. Report-only, so the numbers above stay comparable across runs.
🤖 Generated with Claude Code
https://claude.ai/code/session_01DNoTXU8k3pfSBzR7aJubqL
Generated by Claude Code