Bots that decide whether a job posting is worth applying to #104

Job search means reading far more postings than you'll ever apply to, and most of the signal for "is this worth my afternoon" is already sitting in the posting and in your own CV: years of experience asked for versus held, a tech stack that's a near match instead of exact, a seniority band that creeps past what the title implies, a location or visa line buried in paragraph four. Working that out by hand, one tab at a time, is the actual bottleneck, not writing the application itself.

The mechanical part, lining up a posting's stated requirements against a structured CV, has one right answer a gitbot can just compute. What's left over is a judgment call: a near miss on years or stack might still be worth a shot, a hard mismatch on visa or location usually isn't, and the useful bot surfaces that call ("this is a stretch, here's where") rather than silently filtering the posting out or silently deciding for you that it's fine.

We'd take bots across CV formats (JSON Resume, your own YAML) and posting sources (a job board's listing page, a forwarded posting, an ATS export).

New here? gitbot runs Claude Code, Codex or OpenCode as reusable bots on your own machine, with your logins and your files. You define a bot once, a name and a job in plain English, and run it in as many folders as you like.

npm install -g @gitbot-hq/gitbot
gitbot start

Built one for this? Finished bots go into this library, each listed under the GitHub account that built it. In GitBot, the share menu on a bot has a Publish to Marketplace option that opens the pull request to add it. Your instructions go in as written.

These stay open after the first bot lands. And yours doesn't need to be general: people install the bot that's built for the stack they're already on.