JevX for GitHub
Overview
See which lines in any GitHub repo are hardcoded guesses that should be a Jev judgment, with a fit score for each. Read-only.
JevX finds the judgment calls hiding as rules in code: regexes that guess what an error means, keyword lists that guess what a customer wants, includes() checks that guess intent. Open any GitHub repository, click JevX, and get: The exact file and lines where Jev fits The current code, and the question Jev would ask instead A fit score from your AI, patterns from real Jev projects, and TypeSafe (optional) A plain verdict: "Jev fits here", "could help", "mixed signals" or "not needed" A ready prompt for Claude or a JevX command to apply the change locally, with your tests running before and after Bring your own AI key: Gemini, xAI (Grok) or OpenRouter. Private by design: read-only, keys stay in your browser, code goes only to the AI provider you choose, and secrets are removed first. No tracking, no analytics. Open source (MIT): https://github.com/vij-sameerb5/JevX Website: https://jevx.live
0 out of 5No ratings
Details
- Version0.3.0
- UpdatedOctober 5, 2026
- Offered byshaiksameer8921
- Size46.5KiB
- LanguagesEnglish
- DeveloperSHAIK SAMEER
12-25 Subedar Plaza flat no: 104 vijayawada, Andhra Pradesh 521137 INEmail
shaiksameer8921@gmail.comPhone
+91 73591 23123 - TraderThis developer has identified itself as a trader per the definition from the European Union and committed to only offer products or services that comply with EU laws.
Privacy
JevX for GitHub has disclosed the following information regarding the collection and usage of your data. More detailed information can be found in the developer's privacy policy.
JevX for GitHub handles the following:
This developer declares that your data is
- Not being sold to third parties, outside of the approved use cases
- Not being used or transferred for purposes that are unrelated to the item's core functionality
- Not being used or transferred to determine creditworthiness or for lending purposes
Support
For help with questions, suggestions, or problems, visit the developer's support site