Add jev-belay, jev-commit, jev.nvim, jev-skip and jev-plays-pokemon-red - #23
valentynkit wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe project catalog adds five ChangesProject Catalog
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Feature Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Landed on main as f6c50c8 with you as the commit author, so it shows on your contributions. Live at https://awesomejev.com/#agent-tooling. One of the five was already added by the nightly job, so it was skipped. Closing the PR rather than merging because the site's data file gets appended to nightly, which makes fork branches conflict faster than they can be reviewed. Landing the 4 entries directly keeps your authorship without force-pushing to your fork. Thanks for the submission. |
Five tools of mine built on Jev, all MIT, each calling the API directly: jev-belay, a Claude Code Stop hook that blocks an unverified done; jev-commit, a pre-commit hook that checks the message against the staged diff; jev.nvim, a Neovim plugin that turns a plain-language question into a quickfix list; jev-skip, a YouTube sponsor skipper that works from captions with no crowd database; jev-plays-pokemon-red, Pokemon Red on PyBoy where Jev decides only at branches and calibration is measured. Only data/projects.json touched, npm run validate passes; README and site regenerate in CI.