Run any Skill in Manus with one click

paude-harvest

Stars7

Forks0

UpdatedJune 23, 2026 at 13:53

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

hhellbusch

hhellbusch/my-ai-workspace

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

6 files

SKILL.md

readonly

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

Paude Harvest

Pull committed work from a running paude session into the host repo and merge locally — including submodule SHAs that exist only in the container.

<essential_principles>

Uncommitted container work is invisible to harvest — triage first if diff is empty.
paude harvest often fails on submodule fetch; the fallback path is normal, not exceptional.
Never git submodule update --remote — it discards harvested work.
Verify every commit with git show / git diff — container handoffs can be wrong.
Host 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?

Harvest — pull session into a branch (default)
Merge locally — merge an existing harvest branch into main + submodules
Diagnose — harvest failed or empty diff

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.

| Intent | Workflow | |--------|----------| | Harvest (default) | `workflows/harvest.md` | | Merge locally / `--merge` | `workflows/harvest.md` then `workflows/merge-locally.md` | | Merge only (branch already exists) | `workflows/merge-locally.md` | | Failed harvest / empty diff | Read `references/failure-modes.md`, then `workflows/harvest.md` |

Read referenced workflow files and follow exactly.

<success_criteria>

Harvest branch exists with verified commits
Submodule changes merged on correct default branches
Host main pointers updated without reverting unrelated work
User told what was merged and what remains unpushed </success_criteria>

More from this repository

same repository

review

hhellbusch/my-ai-workspace

Review all pending changes against repo conventions before committing

2026-07-237

validate

hhellbusch/my-ai-workspace

Mark files as human-reviewed with specific validation types

2026-07-227

paude-launch

hhellbusch/my-ai-workspace

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.

2026-06-237

paude-spec

hhellbusch/my-ai-workspace

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.

2026-06-237

paude-triage

hhellbusch/my-ai-workspace

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.

2026-06-237

brief

hhellbusch/my-ai-workspace

Create or update a project BRIEF.md — scaffolds planning structure for work that crosses the 5-file / multi-session threshold

2026-06-237

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

Paude Harvest

Pull committed work from a running paude session into the host repo and merge locally — including submodule SHAs that exist only in the container.

<essential_principles>

Uncommitted container work is invisible to harvest — triage first if diff is empty.
paude harvest often fails on submodule fetch; the fallback path is normal, not exceptional.
Never git submodule update --remote — it discards harvested work.
Verify every commit with git show / git diff — container handoffs can be wrong.
Host main must be fetched/pulled before harvest to avoid stale-base merges.

</essential_principles>

Harvest — pull session into a branch (default)
Merge locally — merge an existing harvest branch into main + submodules
Diagnose — harvest failed or empty diff

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>

Harvest branch exists with verified commits
Submodule changes merged on correct default branches
Host main pointers updated without reverting unrelated work
User told what was merged and what remains unpushed </success_criteria>