agentleFS
jhlee0409jhlee0409/omni-harness-kit/skills/pickup/SKILL.md

pickup

Skill2 starsChanged 4 months agoMITView on GitHub

Re-enter in-flight work in a fresh session by reading a resume block a previous session left (the read half of the handoff/pickup loop). Use at the start of a fresh session, or when the user says "pickup", "resume", "이어서", "재개", "어디까지 했지", "continue where we left off".

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 8 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

  • 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

  • GoogleSkill

    diagnosing-bugs

    Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 28 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Find the resume block: Prefer an active spec's specs/*/context.md ## 0.

    line 17
  2. Distinctive:

    If the block contradicts the repo (says a file was changed but it wasn't), surface the conflict instead of trusting the block blindly.

    line 27

“Common” is measured: kept by at least 6 in 10 of the 28 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

pickup

Re-establish where the work left off — from the resume block ALONE, without asking the user to re-narrate.

  1. Find the resume block. Prefer an active spec's specs/*/context.md ## 0. Resume here block (use the [spec-slug] arg to disambiguate when several exist) — that is where /harness-kit:handoff writes when a spec is active; fall back to .claude/handoff.md. When both exist, use the most recently modified — it is the freshest handoff. If none is found, say so plainly — don't guess.
  2. Read it fully, then re-ground in the repo: git status --short, git log --oneline -5, and read the files it lists. Confirm the stated state matches reality (files actually changed, the next command still makes sense).
  3. Restate the original ask + where you are (phase / N of M) + the single next action — then DO that next action. Do NOT redo the "Don't redo" items.
  4. If the block contradicts the repo (says a file was changed but it wasn't), surface the conflict instead of trusting the block blindly.

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.