agentleFS
Sign inStart free
seanmishraseanmishra/claude-skills/pickup/SKILL.md

pickup

Skill1 starsChanged 6 days agoMITView on GitHub

Resume work from .scratch/handoff.md, or from the backlog when there is none. Use when the user says pick up, or asks to continue from the last session or a handoff.

32 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ai-review, discover and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SkyWalker2506Skill

    ai-review

    This skill should be used when the user asks to "review a PR", "code review", "AI review", "check the pull request", or asks about automated review via OpenRouter or Gemma. Also activates when setting up GitHub Actions for PR review.

    Also in 3 projects that use this

  • anombyte93Skill

    discover

    Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

    Also in 3 projects that use this

  • asterkinSkill

    adr

    Create Architecture Decision Records (ADRs) following project standards. Guides template usage, process, and best practices for documenting architecturally significant decisions.

    Also in 3 projects that use this

  • AWSSkill

    retro

    Conduct a retrospective on a coding session.

    Also in 5 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    design

    Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md
  1. Read the handoff. Read .scratch/handoff.md in the project root. If it is missing, the last session ended at a clean point: read the backlog (the project's own tracker, or .planning/backlog.md), offer its top few entries as a starting point, and wait for the user to pick. With no backlog either, tell the user there is nothing to resume and stop. Mention .scratch/handoff.prev.md only if the user asks about the last handoff. Steps 2 to 5 apply only when a handoff exists. Done when: the file is read, or the user has the backlog's top entries, or knows there is nothing to resume.
  2. Check for drift. Note the handoff's age from its Written date and flag it if it is more than 7 days old. In a git repo, run git log --oneline <sha>..HEAD with the sha it recorded, and compare git status --short with the uncommitted files it listed. Confirm the files and folders it names are where it says. Done when: every commit since the sha, every working-tree difference and every missing path is noted.
  3. Load the skills listed under Suggested skills, and read the backlog entries and docs under Pointers.
  4. Report and wait. In a few lines: the goal, what is done, the first next step, and any drift from step 2. If the handoff is stale, ask whether it still applies. Wait for the user's go-ahead.
  5. Consume the handoff. On the go-ahead, rename .scratch/handoff.md to .scratch/handoff.prev.md, replacing any older one, so the next /pickup can't resume it twice. The session now carries its contents, and /handoff writes a fresh one at the end. Done when: .scratch/handoff.md no longer exists.

Gotchas

  • .scratch/ is gitignored, so a worktree session has none of its own. Look for the handoff in the main checkout's .scratch/ (git worktree list names it first), and rename it there.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free