gw-harvest
Collect, as proposals, what projects using Galivelop-workflow changed or invented (edited workflow skills and scripts, new skills, ideas in their retros) since the last harvest. Use when, from the Gal
SKILL.mdskills/gw-harvest/SKILL.md
GitHubgw-harvest
If .claude/gw/gw-harvest.md exists in the project, read it first: it holds what is specific to the project.
The workflow learns from the projects that use it. retro pushes general ideas from a project; this skill pulls
them, plus anything a project changed in its copy of the workflow. It proposes; it never applies.
Steps
Pick the projects. The projects the user names (or those added to the session), cloned locally. Projects are read-only: never commit, push, edit files or rewrite history in them (updating a dedicated, clean clone with fetch + fast-forward is allowed: it is how you see their latest state), and do not register them as session roots (their same-name skills would shadow this repo's). Clone them read-only into a scratch folder outside the session's working directory. A private project may be added with
add_repo(read access) so the clone works, but never registered (register_repo_root): a registered project loads itsCLAUDE.md,AGENTS.mdand skill list into every call of the session (~17 % of a harvest session's input in one measure). Bring each clone up to date first (git -C <project> fetch && git -C <project> merge --ff-only @{upstream}):recoger.pyharvests the clone'sHEADand warns when it is behind or diverged from its upstream, or has none.Run the mechanical part from this repo:
python3 scripts/recoger.py <project-path> [<project-path> ...]It lists, per project and since the last harvest (
docs/propuestas/estado.json): workflow skills whose body differs, skills born in the project, copied workflow scripts that differ, retro files, the## For Galivelop-workflowsections of every changed.md(pilot notes too, not only retros), the lines there that start with "Propuesta para el flujo" / "Proposal for the workflow" (how projects note requests in their hand-off log), and the commits. A copy equal to an earlier workflow commit is listed apart as an older copy: the project's stale text, never a proposal. If it reports missing history, deepen the clone as it says and run it again.Look at the findings with one subagent per project, all in parallel (one message with several Agent calls), each returning a short summary with paths per finding, never whole files in the main session. For a changed skill,
python3 scripts/recoger.py --diff <skill> <project-path>gives the diff.Classify each finding:
- General: would help any project (a fix, a clearer rule, a missing check, a reusable skill) → proposal.
- Project-specific: domain wording, stack commands, local paths → note it as "stays in the project".
- Already here: the workflow has it in a newer form → note it, no proposal.
Write the proposals in
docs/propuestas/YYYY-MM-DD-<repo-name>.mdusing the template below, in the workflow repo's language for human docs. One file per project and harvest; projects with nothing new go as one line each in another project's file, or in one file of their own when no project brings anything (every version needs a# Harvestfile added since the last tag:python3 scripts/version.py --release).Present them to the user, most valuable first, and wait. What the user approves becomes a normal change in this repo: the piece updated, a CHANGELOG entry and a version bump (patch, minor or major per plan §7).
Record the harvest once the proposals file is committed:
python3 scripts/recoger.py --update-state <project-path> ..., then commitdocs/propuestas/estado.jsonin the same commit as the proposals.
Proposal template
# Harvest <repo> — YYYY-MM-DD
From `<last>` to `<head>` (`scripts/recoger.py`).
## P1. <short title>
- **Source:** `<path>` @ `<commit>` (<skill | script | retro | new skill>)
- **What changes:** <one or two sentences>
- **Why it is general:** <the problem it solves for any project>
- **Version bump:** patch | minor | major
- **Status:** proposed
## Stays in the project
- `<path>`: <why it is project-specific>
Rules
- A proposal cites the exact source path and commit; never paraphrase without a source.
- A project's local edit to a copied workflow file is a signal, not a patch: propose the general version here so the next update reaches every project.
- Don't harvest secrets, personal data or private names into this repo.