@springbrand/hr-cli 0.6.0 → 0.6.1

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
@@ -800,7 +800,7 @@ var recruitingCommands = [
800
800
  {
801
801
  name: "interviews schedule",
802
802
  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.",
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 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
804
  returns: `${InterviewReturns.slice(0, -1)}, ${InviteReturns}`,
805
805
  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
806
  run: async (ctx) => {
@@ -839,7 +839,7 @@ var recruitingCommands = [
839
839
  {
840
840
  name: "interviews reschedule",
841
841
  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.",
842
+ 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
843
  returns: `${InterviewReturns.slice(0, -1)}, ${InviteReturns}`,
844
844
  run: async ({ hr, args, values }) => {
845
845
  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.1",
4
4
  "description": "SpringBrand HR from the command line, for people and Agents.",
5
5
  "license": "UNLICENSED",
6
6
  "type": "module",