evolve(handoff/pickup): handle args and explicit next-step instructions

[baleen37]

Summary

• pickup: Added Step 0 — when the user passes an absolute path after /pickup, use it directly (no AskUserQuestion). When a keyword/phrase is passed, list candidates, match the best one, and confirm with a single question.
• handoff: Added Arguments section — when the user passes text after /handoff, include it verbatim at the top of ## Next Steps labeled (from user at handoff time).

Changes

• plugins/me/skills/pickup/SKILL.md — new Step 0 for args handling
• plugins/me/skills/handoff/SKILL.md — new Arguments section

Evidence

Observed in 3 sessions where /pickup was called with an explicit file path; in one session (ccd0e9e4) AskUserQuestion was rejected because the path was already provided. Observed in 1 session (6e0a9211) where /handoff was called with an explicit next-step instruction that had no documented handling.

Summary by CodeRabbit

• New Features
  • The /handoff command now accepts additional text immediately after invocation, which is inserted as an explicit next-step instruction.
  • The /pickup command now supports optional arguments—provide a file path directly or use keywords to search and match handoff candidates.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: bdf53607-b06d-4785-bb35-b707708917ad

📥 Commits

Reviewing files that changed from the base of the PR and between e09d52f and b163383.

📒 Files selected for processing (2)

• plugins/me/skills/handoff/SKILL.md
• plugins/me/skills/pickup/SKILL.md

---

📝 Walkthrough

Walkthrough

This PR updates the /handoff and /pickup skill documentation to support optional user-provided arguments. The /handoff skill now accepts trailing text as explicit next-step instructions, while /pickup accepts paths or keywords to streamline handoff file selection and confirmation.

Changes

Skill Argument Enhancements

Layer / File(s)	Summary
Handoff argument specification plugins/me/skills/handoff/SKILL.md	Added ## Arguments section defining how user-provided text after /handoff is treated: copied verbatim into ## Next Steps section and labeled (from user at handoff time).
Pickup argument handling plugins/me/skills/pickup/SKILL.md	Added initial "Step 0: Check for args" that routes /pickup behavior based on user arguments: absolute .md paths bypass candidate listing, keywords trigger filtered listing and confirmation, and missing paths produce errors.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• baleen37/bstack#577: Modifies the same plugins/me/skills/pickup/SKILL.md file; this PR adds argument handling while the related PR removes the entire pickup skill documentation.
• baleen37/bstack#592: Updates the same plugins/me/skills/handoff/SKILL.md file; this PR adds argument handling while the related PR deletes the handoff skill documentation entirely.
• baleen37/bstack#628: Also extends /handoff skill documentation behavior to handle user-provided trailing text as explicit next-steps insertion, building on the handoff skill definition.

Poem

🐰 A rabbit scripts two skills so neat,
Where handoff notes and pickup meet,
With arguments now they sing and dance,
No more typing—let's jump the chance! ✨

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fierce-canyon-dijkstra

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}