Repository navigation
fix: remove repo grep, read and tree - #130
Conversation
The Polylane API no longer serves the codefiles search, contents and tree routes these commands called (coreplanelabs/nominal#4531), so they returned 404. Agents read code in their own clone; `repo find` and the GitHub read tools under `tools run` cover finding and fetching it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Warning Polylane could not verify the production impact of this pull request. LGTM: Removed Also considered · 2 refuted
Analysed against 8 cloud accounts and 1 repository
Polylane could not find the cloud resources this repository manages, so this review looked at the entire cloud account. Connect this repository to its resources and the next review will focus on exactly what this code deploys to. Polylane analysed Did this help? React 👍 or 👎 so the next review is sharper. |
There was a problem hiding this comment.
LGTM: no issues found
Reviewed at 2a65245.
For agents
Rationale: The PR removes the three repo commands whose API routes are gone, and nothing in the repo still refers to them; repo show and repo find keep resolveRepoId in use.
Full review
I found no problems: no code, tests or docs still refer to repo grep, repo read or repo tree. The shared resolveRepoId helper is still used by repo show. I didn't run typecheck, lint or the tests here; CI covers those, and the PR reports 563 of 563 tests passing.
Removes
polylane repo grep,repo readandrepo tree, which have returned 404 since Polylane deleted the code index and its codefiles routes. The skill, README and command descriptions no longer promise code search.Why: coreplanelabs/nominal#4531 removed semantic code search and the
repositories.codefiles.search,.contentsand.treeoperations. It is live in nominal 3.83.0 on UAT and prod, so these three commands now fail for every user.Where to look
list,showandfind, which use the repositories API.repois now "Repositories" andtoolslists GitHub reads instead of code search.repo findand leaves the search to a local clone.Feedback wanted: Should
repo readcome back later as a thin wrapper over thegithubFetchFilesagent tool, or ispolylane tools run githubFetchFilesenough?Risk: Scripts calling the three commands now get "unknown command" instead of a 404 from the API. Roll back by reverting; the commands still could not work.
Verified:
npm run typecheck,npm run lintandnpm run test(563 of 563 pass).🤖 Generated with Claude Code