Repository navigation
Clarify skill invocation for source builds and installed tools - #60
Merged
Merged
Conversation
Use the skill-adjacent tiger.dll consistently instead of assuming tiger is on PATH or requiring a repository-relative dotnet run. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c7bc2869-fb5f-451f-a6eb-1289835cbe70
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.
Tiger's skills mixed repository-relative
dotnet runinstructions with examples that assumedtigerwas on PATH. This could send agents down the wrong invocation path even though source launches already register skills beside the built application.Use the absolute, skill-adjacent
tiger.dllconsistently in the CLI and crash-dump skills. This works for both source-build output and installed tool packages, without requiring an apphost or a global Tiger command. Explain the registered output layout and how to handle skills loaded directly from the source tree. No runtime behavior changes.Validation: confirmed the packaged DLL/skill layout and exact packaged skill contents, and ran AzDO and Helix help through the resolved DLL from a non-root working directory. Packaging required suppressing existing NU5119 warnings about hidden dependency files; no packaging changes are included.