Skip to content

Write an agent-runnable upstream sync skill #106

Closed as not planned
Closed as not planned

Description

@ericlitman

Current scope (maintainer, 2026-10-20)

Shrunk. The Cursor pstack 0.15.29 sync (#234) refreshes the "Incorporate a change" steps in UPSTREAM.md from its own run: the per-commit decision table, how to handle files that need review, the verifier registry's skills list, recipe updates, and --wide. This issue no longer waits on #105.

A repository-local sync skill stays unscheduled until a contributor's sync goes wrong because the written steps were not enough.

Original request

Goal

Turn the "Incorporate a change" section of UPSTREAM.md into a repository-local skill that any agent follows to sync Cursor pstack, in Claude Code or Codex, as a maintainer or a contributor. It sits beside verify-open-pstack.

Why the change from Factory (2026-10-12)

The original body asked for a runbook that a Factory planner and builder follow. No Factory branch has merged here since PR #111 on 2026-10-04, and the 0.15.17 sync came from a contributor's fork (#143, PR #145). Contributor-facing tooling should not depend on Factory.

Acceptance criteria

The skill covers these steps, in order:

  1. Open or update the sync issue.
  2. Run upstream-audit.py, upstream-merge.py, the merge probe and the port-patch ledger check (Add a checked port-patch ledger for upstream divergences #105).
  3. Resolve each review row, and record each upstream commit as applied, adapted or excluded.
  4. Update CHANGES.md, NOTICE.md, UPSTREAM.md and README-UPSTREAM.md.
  5. Run the CI-equivalent checks locally: Bun tests, strict typecheck, static invariants and plugin validation.
  6. Run the live gate in Claude Code and Codex through verify-open-pstack.
  7. Merge the reviewed PR, then publish with python3 scripts/release.py publish.

Also:

Order

After #105.

Source: docs/plans/2026-10-01-triage-and-roadmap.md, section 3, item 5, and triage 2026-10-12.

Activity

  1. changed the title [-]Write a factory-runnable upstream sync runbook[/-] [+]Write an agent-runnable upstream sync skill[/+] on Oct 12, 2026
  2. ericlitman commented on Oct 21, 2026

    @ericlitman
    OwnerAuthor

    The shrunk scope shipped: #240 rewrote UPSTREAM.md's "Incorporate a change" steps from the 0.15.29 sync's own run. A repository-local sync skill isn't planned. Reopen this if a sync goes wrong because the written steps were not enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions