v0.5.0 — report-issue skill + ship the scripts skills invoke
What's new
report-issueskill — when Rolester itself looks broken (a crash, stack trace, non-zero exit, or clearly-wrong output), the agent now knows to help you file a bug. It first separates a real defect from a config problem (setup issues route toconfigure/doctor), assembles redacted diagnostics — no candidate PII, comp, employer/recruiter names, or workspace contents, with home paths normalized — and, only with your explicit yes, opens a GitHub issue on this repo under your ownghidentity. It never auto-files and falls back to a prefilled issue URL whenghisn't available. Say "this is broken", "report a bug", or "file an issue".
Fixes
- Ship the scripts the skills actually invoke. The package
filesallowlist shipped onlyinstall-skills.mjs, but skills callnpm run verify:tracker(13×),calibrate:style(9×),scan:sourced,analyze:outcomes, and more — all of which point atscripts/*.mjsthat weren't in the package. So those commands broke in every installed and live copy (the missingverify-tracker.mjsfailure). This release ships all 8 user-facing scripts. If you maintain a live tree,rolester update(orupdate-live) now pulls them in.
Housekeeping
- New packaging guard: a test now fails if any script reachable from a skill or a published
npm runalias isn't in thefilesallowlist (dev-only demo build/deploy scripts exempted) — so this regression class can't ship again. - Docs: backfilled the missing
company-healthentry in the skills reference.
rolester update # or: npm i -g rolester@0.5.0