メニュー
Harvest and locally merge changes from a paude container session. Use when pulling agent work from paude, running paude harvest, merging session commits, importing submodule changes from a container, or fixing failed harvest/submodule fetch.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | paude-harvest |
| description | Harvest and locally merge changes from a paude container session. Use when pulling agent work from paude, running paude harvest, merging session commits, importing submodule changes from a container, or fixing failed harvest/submodule fetch. |
| argument-hint | <session-name> [--slug <task-slug>] [--merge | --no-merge] |
| allowed-tools | Read Write Shell Glob Grep StrReplace |
<essential_principles>
paude harvest often fails on submodule fetch; the fallback path is normal, not exceptional.git submodule update --remote — it discards harvested work.git show / git diff — container handoffs can be wrong.main must be fetched/pulled before harvest to avoid stale-base merges.</essential_principles>
- Narrative guide: `docs/ai-engineering/paude-getting-started.md` - Spec: `.planning/paude-skills/SKILLS-SPEC.md` - Worktrees: `rules/git-worktrees.md` - Submodule init: `rules/submodule-workflow.md` What do you want to do?Parse $ARGUMENTS for intent. If --merge or user said "merge locally", run harvest then merge. If --no-merge, harvest only.
Session name is required — from $ARGUMENTS or ask after paude list.
Read referenced workflow files and follow exactly.
<success_criteria>
Review all pending changes against repo conventions before committing
Mark files as human-reviewed with specific validation types
Start a paude container session for fire-and-forget agent work. Use when creating a paude session, delegating a task to paude, running work in an isolated container, setting up a paude worktree, or launching pi/claude/gemini in podman.
Write a task spec file for a paude container agent. Use when delegating work to paude, preparing a paude prompt-file, writing fire-and-forget agent tasks, or scoping submodule work for harvest.
Diagnose a running or stalled paude container session. Use when paude seems stuck, harvest returned empty, checking paude status, debugging 403 proxy blocks, or deciding wait vs harvest vs reset.
Create or update a project BRIEF.md — scaffolds planning structure for work that crosses the 5-file / multi-session threshold