pickup

Codex pickup checklist when starting on a task.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 5, 2026

When & Why to Use This Skill

The Codex Pickup skill is a specialized context-rehydration utility designed to streamline the transition when starting or resuming technical tasks. It provides a structured framework for developers and AI agents to quickly synchronize with the current state of a repository, including git status, pull request feedback, active terminal sessions (tmux), and testing progress, effectively eliminating 'startup friction' and ensuring no critical context is missed.

Use Cases

  • Task Resumption: Quickly regain focus and context when returning to a complex coding task after a break or weekend by auditing local changes and environment state.
  • Collaborative Handoffs: Seamlessly take over work from another developer or agent by reviewing PR comments, failing CI checks, and recent documentation updates.
  • Session Recovery: Reattach to persistent background processes and terminal sessions using tmux commands to verify the status of long-running tasks or servers.
  • Workflow Planning: Generate a prioritized 2-3 step action plan based on the immediate findings from the repository and CI/CD status to ensure efficient execution.
namepickup
descriptionCodex pickup checklist when starting on a task.

Pickup

Purpose: rehydrate context quickly when you start work.

Steps:

  1. Read AGENTS.MD pointer + relevant docs (run ./scripts/docs-list.ts if present).
  2. Repo state: git status -sb; check for local commits; confirm current branch/PR.
  3. CI/PR: gh pr view <num> --comments --files (or derive PR from branch) and note failing checks.
  4. tmux/processes: list sessions and attach if needed:
    • tmux list-sessions
    • If sessions exist: tmux attach -t codex-shell or tmux capture-pane -p -J -t codex-shell:0.0 -S -200
  5. Tests/checks: note what last ran (from handoff notes/CI) and what you will run first.
  6. Changelog + docs: skim recent updates for context, but do not rely on them alone.
  7. Plan next 2–3 actions as bullets and execute.

Output format: concise bullet summary; include copy/paste tmux attach/capture commands when live sessions are present.