py/ai-job-search
1
0 Fork 0
mirror of https://github.com/MadsLorentzen/ai-job-search.git synced 2026-11-02 13:12:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(apply,rank): route matching portal URLs to installed CLI detail before WebFetch (#535) (#562)

Browse Source 
* fix(apply,rank): route matching portal URLs to installed CLI detail before WebFetch (#535)

When given a URL belonging to an installed portal (e.g. LinkedIn, Jobnet), WebFetch frequently encounters login walls, bot-detection blocks, or 403s. Installed portal CLIs under .agents/skills/ already provide a dedicated detail command that fetches clean posting text and structured metadata directly from board APIs.

- In .claude/commands/apply.md Step 0, invoke the matching installed portal CLI's detail command first, falling back to WebFetch on failure.

- In 09-web-research.md, place the installed portal CLI detail command as the first rung of the escalation order, bumping framework_version to 1.1.2.

- In .claude/commands/rank.md Step 2, align scoring agents to use the portal CLI's detail command before WebFetch.

- In tests/test_apply_host_check.py, add spec and resolution tests ensuring portal CLI detail precedence is strictly asserted and verified.

* fix(apply,rank): route matching portal URLs to installed CLI detail before WebFetch (#535)

When given a URL belonging to an installed portal, WebFetch frequently encounters login walls, bot-detection blocks, or 403s. Installed portal CLIs under .agents/skills/ already provide a dedicated detail command that fetches clean posting text and structured metadata directly from board APIs.

- In .claude/commands/apply.md Step 0, invoke the matching installed portal CLI's detail command first, falling back to WebFetch on failure. Derive matching portal skills from board hosts in cli/src and url-reference.md.

- In 09-web-research.md, place the installed portal CLI detail command as the first rung of the escalation order, update subsequent step references, and bump framework_version to 1.1.2.

- In .claude/commands/rank.md Step 2, align scoring agents to use the portal CLI's detail command before WebFetch.

- In CHANGELOG.md, record the framework_version bump (1.1.1 -> 1.1.2) under [Unreleased] / ### Changed.

- In tests/test_apply_host_check.py, add spec and dynamic resolution tests ensuring portal CLI detail precedence is strictly asserted and verified across all discovered installed skills.
This commit is contained in:
Ahmed authored and GitHub committed 2026-10-15 18:12:33 +02:00
1 parent 7dfa3b66fd
commit e2b966d0e7
5 files changed
+118 -13
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

CHANGELOG.md
+8
View File
@@ -29,6 +29,14 @@ per-file diff commands.
### Changed
- **`/apply` and `/rank` route matching portal URLs to installed CLI `detail` before `WebFetch`**
(#535, `.claude/commands/apply.md` Step 0, `.claude/commands/rank.md` Step 2,
`.claude/skills/job-application-assistant/09-web-research.md`) - job portal URLs pasted
into `/apply` or evaluated in batch by `/rank` now invoke the matching installed portal CLI's
`detail <url> --format plain` command first, avoiding bot-detection 403s and login walls on
aggregator boards before falling back to `WebFetch`. Escalation order in `09-web-research.md`
places portal CLI detail as the first rung (`framework_version: 1.1.1 -> 1.1.2`).
- **`/apply` Step 5e names explicit cleanup shell commands for build intermediates**
(#531, `.claude/commands/apply.md`) - the step previously described deleting `.aux`/`.log`/`.out`
in prose, leaving artifact cleanup vulnerable to being skipped by agents. It now specifies explicit