LaterbaseLaterbase
Sign inGet started

Skill

/laterbase:recommend

What to do next

Recommend the three pins most worth doing next in this repo, with a reason for each. Use when the user asks what to work on, what matters most, or for a recommendation.

Try it

Type /laterbase:recommend in Claude Code, or ask in your own words:

  • What should I work on next?
  • What matters most in the backlog?

What the agent does

Recommend three pins, best first, and let the user pick.

  1. Get the repo as owner/name from git remote get-url origin.
  2. Call search_pins with that repo, ready: true and limit: 15. It lists open pins nothing open blocks, by priority.
  3. Boost pins that touch what the user is working on: list files changed on this branch (git diff --name-only $(git merge-base HEAD origin/HEAD), or recent commits) and call pins_near with them.
  4. pins_near also returns claimed and blocked pins: drop a claimed one unless the user holds the claim, and a blocked one (it has blocked_by) unless you recommend what blocks it. Prefer a mix: the highest priority, the riskiest open issue, and one near the current work.
  5. Reply with three lines, each: key, title, scope, and one sentence on why now. End by asking which one to start; don't claim anything until they choose.

Tools it uses

search_pinspins_near

SKILL.md

Exactly what the plugin installs for Claude Code.

--- name: recommend description: Recommend the three pins most worth doing next in this repo, with a reason for each. Use when the user asks what to work on, what matters most, or for a recommendation. --- # What to do next Recommend three pins, best first, and let the user pick. 1. Get the repo as `owner/name` from `git remote get-url origin`. 2. Call `search_pins` with that `repo`, `ready: true` and `limit: 15`. It lists open pins nothing open blocks, by priority. 3. Boost pins that touch what the user is working on: list files changed on this branch (`git diff --name-only $(git merge-base HEAD origin/HEAD)`, or recent commits) and call `pins_near` with them. 4. `pins_near` also returns claimed and blocked pins: drop a claimed one unless the user holds the claim, and a blocked one (it has `blocked_by`) unless you recommend what blocks it. Prefer a mix: the highest priority, the riskiest open issue, and one near the current work. 5. Reply with three lines, each: key, title, scope, and one sentence on why now. End by asking which one to start; don't claim anything until they choose.