freehire-search: document the OR and title: operators in -q (#674)

* freehire-search: document the OR and title: operators in -q

freehire's search now parses two operators in q: uppercase OR between
up to five alternatives (a union, filtered and paged as one result),
and a leading title: that restricts an alternative to the job title.
The CLI already passes -q through unchanged, so both work today; this
tells the agent they exist, in SKILL.md, --help, the CLI README and
url-reference.md.

* changelog: place the #674 entry under [Unreleased]

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Mads Lorentzen <madslorentzen_17@hotmail.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
authored and GitHub committed 2026-10-19 19:28:29 +02:00
1 parent f24bf85172
commit 60379dfed4
5 files changed
+40 -2

No files matched your search

+9
View File
@@ -13,6 +13,15 @@ per-file diff commands.
## [Unreleased]
### Changed
- **`freehire-search` documents the `OR` and `title:` query operators** (#674,
`.agents/skills/freehire-search/SKILL.md`, `url-reference.md`, `cli/README.md`, `--help`) -
freehire's search parses an uppercase `OR` between up to five alternatives and a leading `title:`
per alternative, but nothing told the agent, so "Go or Rust" became two searches merged by hand
or `-q "golang rust"`, which returns fewer jobs than `golang` alone. Measured live: `golang`
3,550, `golang OR rust` 6,805. The CLI already passes `-q` through unchanged.
### Fixed
- **`freehire-search detail` no longer asks the API for a slug cut out of a URL on another