Jev code snippet selection asks which supplied fragment shows the behavior a developer wants to inspect. A function name is not always the phrase used in the task. Our account function is called enrol, while the task asks about rejecting an empty signup email. The model reads the visible operation and chooses a fragment ID.
Local code then returns the original path and snippet as reading context.
The fixture contains only three fragments. One checks whether an email is blank before calling createUser. Another calls sendResetLink. The third returns a sign-in form. These small snippets make the decision inspectable: you can see the relevant operation and compare it with the question. They are not a complete application, and the blank-email guard is not a general email-address validator.
An API-collected X post about retrieving useful code before a coding agent reads it inspired this example. We read the maintainer documentation for related Jevgrep implementations to check the workflow boundary. Those tools can search authorized repositories and return source context. This page demonstrates selection from explicitly supplied fragments.
It does not install a CLI, scan your project or reproduce the source author's context and cost measurements.