Repository navigation
Add a repository execution preflight to Agentmetry scan - #441
Merged
Merged
Conversation
Inventory project declarations that can launch code during startup, workspace open, package installation and container setup. Show unresolved references and partial coverage without executing repository code or exposing manifest values. Keep the preflight behind an explicit scan flag and cover the CLI, supported manifests, link handling and input limits with synthetic fixtures.
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.
A repository can declare code that runs when an agent starts, an editor opens
a folder, or a developer installs dependencies. Those declarations can exist
before Agentmetry sees an agent tool call.
agentmetry scan --preflight PATHinventories Claude startup hooks, projectMCP definitions, VS Code folder-open tasks, npm install lifecycle scripts and
devcontainer lifecycle fields. It reports the declaration's location and
whether a simple local script reference could be found. The JSON output
includes partial coverage for unreadable manifests, links and scan limits.
The scanner reads supported manifests and checks file metadata. A script shown
as present remains uninspected. The report omits command text, environment
values and endpoint URLs. The existing scan modes keep their behavior.
Validation