Skip to content

v0.0.3

Latest

Choose a tag to compare

@github-actions github-actions released this 25 Oct 19:53
· 23 commits to main since this release
b67b11f

A new change gets its intent instead of going to pending

When a record started a new change, the model had to put the intent under the name it had just chosen for the change. It often put it under the changed paths instead, as on a rename or a commit that touched many files. record then couldn't use the reply, put the edits in a change called pending with an empty intent, and build refused until you ran patchbook intent. Now the reply has its own field for the new change's intent, so the model has no key to guess. Replaying real prompts, a one-file rename went from 10 of 10 replies unusable to 0 of 10 (#319).

The model sees a rename or a copy as one

The intent for a recorded move was written from a diff that showed the new path as an added file, listed twice, and never named the old path. A copy showed as a whole new file. So the intent described a new skill instead of the rename or where the files came from. Now the model sees the edit line, such as move skills/a -> skills/a2 or copy extra/skills/x -> skills/x, and only what you changed in the file, diffed against the moved file (#320).

Status and build count every edit

status and build printed <n> edits apply, and status --json reported applied, but the count left out add, replace, delete, move and copy edits. A change that vendored a skill with a copy edit reported 0. Now the count includes every edit that applies, once, however many outputs it reaches, and a later edit that deletes, replaces or moves its file doesn't undo it: a block entry in a file that a copy also writes elsewhere is one edit. A copy or move of a folder is one edit, as CHANGE.md lists it (#321).

Record names the change and writes its intent when the model can't

When the model failed, as with a reply patchbook can't use, a timeout, no claude or codex CLI, or intent.provider = none, record and the commit hook put the edits in a change called pending with an empty intent. status reported it as a problem, and build and the hook's build refused until you ran patchbook intent. Now patchbook names the change from its edits and writes an intent that says what they do, so the build goes ahead:

$ PATCHBOOK_PROVIDER=none git commit -qm "rename a"
rename-skills-a-to-skills-a2: Renames skills/a to skills/a2. Edits skills/a/SKILL.md.
move     skills/a -> skills/a2
file     a2/SKILL.md
intent   by patchbook for rename-skills-a-to-skills-a2 (intent.provider is none). To replace it, run `patchbook intent rename-skills-a-to-skills-a2` or edit its line to `intent: <yours>`

CHANGE.md labels that line intent (by patchbook):, and status lists the change as a note, not a problem. To replace the intent, run patchbook intent <name>, or rewrite the line as intent: .... While the model fails, the edits always go to a new change or the one you name, never to an existing change the model would have picked. A new block entry still gets an empty intent, and build refuses until patchbook intent fills it. A pending change that 0.0.1 recorded keeps its name, and its intent stays empty until you fill it or a later record adds to that change.

What's Changed

  • fix(record): the model writes the new intent in its own reply field by @willgosnold in #325
  • fix(record): the model reads a recorded move or copy as one by @willgosnold in #326
  • fix(status): count add, replace, delete, move and copy edits as applied by @willgosnold in #322
  • fix(verify-patchbook): clean a sandbox when TMPDIR ends in a slash by @willgosnold in #323
  • test(qa): script dogfooding journeys, with a fake or the real model by @willgosnold in #324
  • ci: stop running the qa journeys by @willgosnold in #332
  • feat(record): write the intent from the edits when no model can by @willgosnold in #330
  • docs(changelog): move this week's entries to 0.0.3 and add #319 and #320 by @willgosnold in #333

Full Changelog: v0.0.2...v0.0.3