Repository navigation
fix: scope agent rule discovery to instruction paths - #222
Merged
Merged
Conversation
nettapper
approved these changes
Oct 2, 2026
nettapper
enabled auto-merge (squash)
October 2, 2026 18:46
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
Rule discovery currently scans all Markdown beneath
.claude,.codex, and.gemini, loading skill bodies, references, commands, and cached plugin content into the initial prompt as rules. A synthetic workspace with 100 skills produces a 3.17 MB prompt even though skill discovery already exposes metadata separately.Restrict rule discovery to each agent's
rules/directory and explicit instruction files. The same fixture produces about 20 KB while retaining all 100 skills in discovery. Preserve instruction bootstrap order, namespaces, and selectors, and include Gemini's style guide once.Compatibility: other rule Markdown under these agent directories must move into
rules/or.agents/rules/. The search-path documentation includes migration instructions.Validation
go test -race ./pkg/...go test ./...in a network-disabled local container with an empty default home, avoiding unrelated installed user skills.make lint; unrelated baseline formatting changes excluded.Based on upstream
c772470.