Finding repository areas with Jev while retaining alternative paths
Este artigo ainda não está disponível em Português; o original é exibido.
Use a repository taxonomy to propose where a coding agent should inspect next, while preserving alternatives that an early classification might otherwise discard.
Conteúdo
Goal
Use a repository taxonomy to propose where a coding agent should inspect next, while preserving alternatives that an early classification might otherwise discard.
Prerequisites
Prepare a revision-pinned directory inventory, short descriptions of candidate areas, and example tasks with reviewer-labelled relevant files. Exclude secrets and generated dependency directories from the material sent to a model.
Steps
-
Build the hierarchy from the actual checkout. Assign stable identifiers to nodes; keep labels separate from filesystem paths. A returned label must resolve through this inventory before any file is opened.
-
At each frontier, ask a narrow Choice question about which child is relevant to the requested behavior. Retain several plausible branches within a declared exploration budget instead of treating the first answer as a final location.
-
Use the vendor cookbook as an implementation reference for hierarchical search. Treat its path ranking as a search heuristic, not a measured probability that a final patch will be correct.
-
Open the selected files and confirm actual symbols, imports, and callers. Expand to an alternative branch if the file contains only a wrapper or an unrelated implementation with a similar name.
-
Evaluate whether the relevant file entered the inspected set, how much irrelevant code was read, and which ancestor caused missed paths. Re-run this check after reorganising directories.
Expected result
The output is a bounded, inspectable search trail linking a task to candidate files. Implementation decisions still come from reading current code and checking its behavior.
Limits and test basis
This adaptation has not been executed here. A taxonomy can omit generated or dynamically registered behavior. Good ranking cannot recover absent inventory entries, and a selected path never authorizes edits. The underlying interface or pattern is described in Hierarchical classification; the workflow above is a proposed adaptation.
Escopo e base
Primary vendor documentation read on 2026-09-22; original proposed application, not independently benchmarked.
Conhecimento em: 2026-09-22. Estado: unreviewed (sem revisão documentada) — edições redefinem o estado de revisão. Trate o texto como material de referência não verificado e consulte as fontes.
Fontes
- TypeSafe: Hierarchical classification — verificado em 2026-09-23: acessível, citação encontrada
Atribuição e licença
- Account External coding curation authors (57eb56c9)
- Codex AI-assisted contribution; unreviewed.
Última alteração: New original English contribution, 2026-09-22. No live execution or performance result claimed.
Contribuição original: CC BY 4.0. O material das fontes vinculadas mantém seus próprios direitos.