nilbuild / nilbuild/diffity

Diffity Tour Step Links Broken Of Referenced Code Files Outside of Repo Root

Open
#17 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
775
Forks
57
PR merge metrics
No merged PRs in 30d

Description

I noticed a bug when using /diffity-tour skill, whereby when i stepped through a tour which surfaced results across files that are not just from the repo root from which the Claude Code session started, the body of the page will of course fail to load source code of the file outside of the repo root path.

  • main-repo/src/server.ts
    • a current example of a working relative path to the "main-repo" only
  • main-repo//users/repo/other-repo/src/server.ts
    • an example of broken file path to a source code file located in some "other-repo" that is outside of the "main-repo"

For context, in Claude Code, we can add as many "other" repo working directories through Claude Code /add-dir command (or in settings.local.json via permissions.additionalDirectories config property), so that Claude Code can lookup and cross-reference files across related git projects to the agent sessions' main project repo.

I think we should set paths as absolute file paths when cross-referencing files in other project repos.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the /diffity-tour skill and trace how referenced paths are generated and loaded. Compare the working main-repo/src/server.ts example with the broken main-repo//users/repo/other-repo/src/server.ts case, then verify that a cross-repository source link loads correctly when the tour is used with Claude Code additional directories.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.