@springbrand/hr-cli 0.6.0 → 0.6.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -28,7 +28,8 @@ The rules below are what the help cannot tell you.
28
28
 
29
29
  ## Interviews, meetings and calendars
30
30
 
31
- - HR connects to no meeting platform or calendar. When the user wants an online interview, first create the meeting with the tool you have for the user (Feishu, Tencent Meeting, Zoom…), then book it in HR with that meeting's link (and its ID) as the place. For an in-person interview, pass the address.
31
+ - When the user asks to invite a candidate to an interview, book it in HR: HR mails the invitation itself. You need the time and whether it is online or in person; if the user did not say which, ask.
32
+ - HR connects to no meeting platform or calendar. For an online interview, unless the user names another platform or gives a link, create a Feishu meeting first with `lark-cli` (read `lark-cli skills read lark-calendar` once): `lark-cli calendar +create --as bot` at that time, titled with the candidate and the round, with the interviewers as attendees (it comes with a video meeting); then `lark-cli calendar +get --as bot` on that event for the meeting's join link, `https://…/j/<number>`. Book it in HR with that link (`--online`) and the number (`--code`) as the place. Never use the event's own link or a share link: the candidate cannot join with it. Never reuse the link of another interview, even a cancelled one. If no join link came back, tell the user instead of booking without one. For an in-person interview, pass the address.
32
33
  - Booking (and moving) an interview may mail the candidate an invitation with the time, place and link, when the job's stage is set to. Say so to the user only when `data.invite` says it was sent; `pendingApproval` there means the invitation waits for a person in IAM, though the interview is booked.
33
34
  - HR then waits for the candidate's answer, reminds them and gives up on its own, as the stage says. Never mail the candidate a second invitation yourself.
34
35
  - When an interview moves or is cancelled, change HR first (`reschedule`, `cancel`), then the meeting and any calendar event.
package/dist/hr.js CHANGED
@@ -145,6 +145,7 @@ var Options = {
145
145
  page: { type: "string" },
146
146
  "page-size": { type: "string" },
147
147
  wait: { type: "boolean" },
148
+ "daily-review": { type: "string" },
148
149
  "no-browser": { type: "boolean" },
149
150
  timeout: { type: "string" },
150
151
  start: { type: "string" },
@@ -526,7 +527,7 @@ var coreCommands = [
526
527
  // src/commands/jobs.ts
527
528
  var JobStatuses = ["draft", "open", "paused", "closed"];
528
529
  var EmploymentTypes = ["full_time", "part_time", "contract", "intern"];
529
- var JobFields = "slug, departmentId, hiringManagerPrincipalId, recruiterPrincipalId, headcount, location, descriptionMd, pipelineId, scorecardId, keywords [], requiredDegree, skills [{ name, level 1-10 }], members [{ principalId, role interviewer|viewer }]";
530
+ var JobFields = "slug, departmentId, hiringManagerPrincipalId, recruiterPrincipalId, headcount, location, descriptionMd, pipelineId, scorecardId, keywords [], requiredDegree, dailyReview, skills [{ name, level 1-10 }], members [{ principalId, role interviewer|viewer }]";
530
531
  var JobReturns = "data: the job { id, title, slug, status, employmentType, pipelineId, scorecardId, stages, members, skills, \u2026 } with url.";
531
532
  async function jobFlags(ctx) {
532
533
  const { hr, values } = ctx;
@@ -539,6 +540,7 @@ async function jobFlags(ctx) {
539
540
  descriptionMd: values.description,
540
541
  recruiterPrincipalId: values.recruiter ? await personId(hr, values.recruiter) : void 0,
541
542
  keywords: list(values.keywords),
543
+ dailyReview: values["daily-review"] === void 0 ? void 0 : oneOf("--daily-review", values["daily-review"], ["on", "off"]) === "on",
542
544
  ...interviewers ? { members: interviewers.map((principalId) => ({ principalId, role: "interviewer" })) } : {}
543
545
  };
544
546
  }
@@ -559,8 +561,8 @@ var jobCommands = [
559
561
  },
560
562
  {
561
563
  name: "jobs create",
562
- usage: "hr jobs create --name <title> [--status draft|open|paused|closed] [--kind full_time|part_time|contract|intern] [--location <text>] [--description <markdown>] [--with <interviewers>] [--recruiter <person>] [--keywords <a,b>] [--json '{\u2026}']",
563
- does: `Open a job. --with sets its interviewers, --recruiter its recruiter, --keywords the words that route mail to it. Mail to jobs+<slug>@ the recruiting domain lands on it.${takesJson(JobFields)}`,
564
+ usage: "hr jobs create --name <title> [--status draft|open|paused|closed] [--kind full_time|part_time|contract|intern] [--location <text>] [--description <markdown>] [--with <interviewers>] [--recruiter <person>] [--keywords <a,b>] [--daily-review on|off] [--json '{\u2026}']",
565
+ does: `Open a job. --with sets its interviewers, --recruiter its recruiter, --keywords the words that route mail to it, --daily-review on sends its recruiter (through Eve) a few resumes waiting for screening each workday at 10:00 China time, six a day across all their jobs. Mail to jobs+<slug>@ the recruiting domain lands on it.${takesJson(JobFields)}`,
564
566
  returns: JobReturns,
565
567
  run: async (ctx) => {
566
568
  const body = await bodyOf(ctx, await jobFlags(ctx));
@@ -570,7 +572,7 @@ var jobCommands = [
570
572
  },
571
573
  {
572
574
  name: "jobs update",
573
- usage: "hr jobs update <job> [--name <title>] [--status \u2026] [--kind \u2026] [--location <text>] [--description <markdown>] [--with <interviewers>] [--recruiter <person>] [--keywords <a,b>] [--json '{\u2026}']",
575
+ usage: "hr jobs update <job> [--name <title>] [--status \u2026] [--kind \u2026] [--location <text>] [--description <markdown>] [--with <interviewers>] [--recruiter <person>] [--keywords <a,b>] [--daily-review on|off] [--json '{\u2026}']",
574
576
  does: `Change a job; fields left out keep their value. --with replaces the interviewers. Switching pipelineId moves its applications to the stage of the same category.${takesJson(JobFields)}`,
575
577
  returns: JobReturns,
576
578
  run: async (ctx) => linkedOne(ctx.hr, await ctx.hr.patch(`/jobs/${await requiredJob(ctx.hr, joined(ctx, "a job"))}`, await bodyOf(ctx, await jobFlags(ctx))), "jobs")
@@ -800,7 +802,7 @@ var recruitingCommands = [
800
802
  {
801
803
  name: "interviews schedule",
802
804
  usage: "hr interviews schedule <name|id> --start <time> [--end <time> | --minutes n] (--online <link> [--code <meeting id>] | --offline <address>) [--with <people>] [--job <job>]",
803
- does: "Book an interview for a candidate waiting in `hr interviews to-schedule` (or an application id). <time> is ISO 8601 with its UTC offset, such as 2026-11-12T15:00+08:00. Length defaults to 60 minutes. Where: --online with the meeting link from any platform (Feishu, Tencent Meeting, Zoom\u2026; create the meeting first with your calendar tool) and optionally its meeting ID, or --offline with the address. <people> are interviewers, comma-separated names, emails or ids from `hr people search`; leave it out to use the stage's default interviewers, or else the job's interviewers. When the stage is set to, HR mails the candidate the invitation (time, place, link) in their thread and waits for their answer; it puts nothing on any calendar.",
805
+ does: "Book an interview for a candidate waiting in `hr interviews to-schedule` (or an application id). <time> is ISO 8601 with its UTC offset, such as 2026-11-12T15:00+08:00. Length defaults to 60 minutes. Where: --online with the join link (and --code the number) of a meeting created for this interview, on any platform (for Feishu, create it with `lark-cli` as the saas-hr-cli skill says), or --offline with the address. Never reuse the link of another interview, even a cancelled one: every change mails the candidate again. <people> are interviewers, comma-separated names, emails or ids from `hr people search`; leave it out to use the stage's default interviewers, or else the job's interviewers. When the stage is set to, HR mails the candidate the invitation (time, place, link) in their thread and waits for their answer; it puts nothing on any calendar.",
804
806
  returns: `${InterviewReturns.slice(0, -1)}, ${InviteReturns}`,
805
807
  example: 'hr interviews schedule "Li Wei" --start 2026-11-12T15:00+08:00 --online https://vc.feishu.cn/j/324385898 --code "324 385 898"',
806
808
  run: async (ctx) => {
@@ -839,7 +841,7 @@ var recruitingCommands = [
839
841
  {
840
842
  name: "interviews reschedule",
841
843
  usage: "hr interviews reschedule <interview id> [--start <time>] [--end <time> | --minutes n] [--online <link> [--code <meeting id>] | --offline <address>]",
842
- does: "Move or relocate an interview. A new --start keeps the length unless --end or --minutes is given. A new time or place mails the candidate the invitation again and asks them to confirm again.",
844
+ does: "Move or relocate an interview. A new --start keeps the length unless --end or --minutes is given; a new time alone keeps the meeting link. A new time or place mails the candidate the invitation again and asks them to confirm again, so pass a new link only for a meeting created for this interview, never one from another interview.",
843
845
  returns: `${InterviewReturns.slice(0, -1)}, ${InviteReturns}`,
844
846
  run: async ({ hr, args, values }) => {
845
847
  const id = needed("an interview id", args[0]);
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@springbrand/hr-cli",
3
- "version": "0.6.0",
3
+ "version": "0.6.2",
4
4
  "description": "SpringBrand HR from the command line, for people and Agents.",
5
5
  "license": "UNLICENSED",
6
6
  "type": "module",