Repository navigation
Conversation
Contributor
|
Thanks @rs545837 for contributing a tool example — visible, reviewable PRs like this grow the reference for everyone. What happens next
More ways to help — loop-engineering maintainers |
Owner
|
Leaving this open. The merge state is UNSTABLE, and there is no approving review. |
This branch has not been deployed
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
I'm the maintainer of Sem. This adds an optional MCP cookbook entry for report-only local code navigation: locate an entity, request related source, record incomplete evidence, and hand off before changing code.
Three example files only; no default tools, runtime behavior, skills, registry or permissions changed. The pinned stdio configuration requires an explicit trusted checkout. The guide warns that the full server is not read-only, that repository selection is not a sandbox, and that structural evidence does not replace builds/tests.
Verification
An independent agent followed the repository's loop-verifier skill and approved the scoped contribution for maintainer review:
git diff --checkpassed.sem_findreturnedparse_configatconfig.py:1.load_configcaller with no tool error.Content-only contribution (CONTRIBUTING path A); application/tool package suites were not run. This verifies the connector, not session-speed claims.
Checklist
AI assistance was used for implementation and verification. Maintainer review is requested; no auto-merge.