Repository navigation
chore(upstream): merge cursor/plugins - #28
Merged
Merged
Conversation
Removes the sentence "Don't hand back a rewritten prompt." from the sharpen skill and regenerates the Claude Code copy, mirroring everysphere #1147012.
Co-authored-by: Cursor Agent <[email protected]>
…or#715) * feat(pstack): offer /create-formal-verification-skill in /setup-pstack Ask once at the end of setup whether the user wants a formal verification skill, unless the project already has one. On yes, run /create-formal-verification-skill. The offer matches the existing /create-verification-skill offer. Co-authored-by: lauren <[email protected]> * Sync poteto-help and the pstack guide with shipped skills Document /create-formal-verification-skill, the setup-pstack formal verification offer, /ketchup, /sharpen, /in-your-own-words, the Claude Code install, the Opening a PR playbook, the verification skill Helpers section, and Babysit's Origin path. Co-authored-by: lauren <[email protected]> * Regenerate the Claude Code pstack harness tree Co-authored-by: lauren <[email protected]> --------- Co-authored-by: Cursor Agent <[email protected]>
…cret-copy zoom: require Client Secret with Client ID (1.0.2)
[meta-ads] Add Meta Ads plugin
…al-verification-skill (cursor#721) The event-order sentence names TLA+ as the default in any language, and the sentence that recommended TLA+ for concurrent and distributed designs is gone. When no verifier runs on the language, the agent says so and tests the real code with generated inputs, not a hand model of the function. The new paragraph is the exact text that a preregistered eval tested. Co-authored-by: Cursor Agent <[email protected]>
* Record covered code and sync commit in formal verify skills create-formal-verification-skill now writes, into the generated verify skill, which files and functions each check covers and the commit at which the verification was last confirmed to describe them, so a later agent can see when covered code has changed since. Co-authored-by: lauren <[email protected]> * Add maintain-formal-verification-skill Upkeep loop for a formal verify skill: read the commits that touched covered code since the recorded sync commit, update the model, harness, or properties from the code, rerun, prove each updated check can still fail, and report each check as in sync, updated, bug, or blocked. Listed in the README and in the poteto-help routing table. Co-authored-by: lauren <[email protected]> * Find the formal verify skill by what it does, not by name create-formal-verification-skill gives the generated skill no fixed name, and setup finds it by its description. The maintain skill now does the same. Co-authored-by: lauren <[email protected]> * Name maintain-formal-verification-skill in the formal verification docs Adds the skill to the spots that already cover formal verification: the verify-and-ship section, the special-cases sentence on guide page 9, and the poteto-help state check and recipe. Co-authored-by: lauren <[email protected]> * Point the guide page 9 link at the formal verification section Co-authored-by: lauren <[email protected]> * Keep the sync commit in place for a blocked check maintain-formal-verification-skill set the sync commit to the checked commit for every check, including a blocked one. A blocked check was not confirmed to describe the code, so moving its sync commit hides the drift from the next pass. Step 6 now leaves it in place and says so in the report. Step 2 now points at step 5, where a failure is judged. Co-authored-by: lauren <[email protected]> --------- Co-authored-by: Cursor Agent <[email protected]>
…ation-skill (cursor#724) * docs(pstack): match guide page 6 to create-formal-verification-skill's tool choice cursor#721 made TLA+ the default for event-order questions in any language, and added a fallback: when no verifier runs on the language, the agent says so and tests the real code with generated inputs. The guide's tool-choice paragraph still described the old wording. Claude Code harness copy regenerated. Co-authored-by: lauren <[email protected]> * chore(pstack): bump to 0.15.28 Co-authored-by: lauren <[email protected]> --------- Co-authored-by: Cursor Agent <[email protected]>
Co-authored-by: Cursor <[email protected]>
…ror 2. Co-authored-by: Cursor <[email protected]>
…tools X plugin: livestream tools (sources, broadcasts, scheduled broadcasts, chat moderation)
…ite (cursor#729) * pstack: restore /sharpen to the original prompt, plus one line to leave choices open Co-authored-by: lauren <[email protected]> * pstack: say /sharpen returns a rewritten prompt and doesn't do the task Co-authored-by: lauren <[email protected]> * chore(pstack): bump to 0.15.29 Co-authored-by: lauren <[email protected]> * pstack: put /sharpen's four asks in a numbered list Drops the semicolons and the (1) to (4) markers that broke technical-writing and unslop rule 13. Adds "do four things" so a complete sentence introduces the list. Every other word is unchanged. Co-authored-by: lauren <[email protected]> --------- Co-authored-by: Cursor Agent <[email protected]>
Co-authored-by: Cursor <[email protected]>
X plugin: broadcast chat history (get_broadcast_chat) and chat summaries
Resolved pstack/skills/setup-pstack/SKILL.md by keeping the port's version and adding upstream's new formal verification offer as step 7, worded the port's way: read the skill and follow it, instead of invoking it wherever Cursor installed pstack.
It uses no Cursor terms, but it finds and updates a project-local verify skill, so it gets the pstack-harness pointer that says where to search for one in both harnesses. It is user-only, so it also gets the Codex policy file. The README now pairs each verification skill with its maintain skill.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upstream: cursor/plugins@a66a8931c2dd
Closes #24.
merge-upstream.pystopped on a conflict that needed a person, so this pull request finishes that merge by hand. Upstream has moved past the issue's88d4751since then, but the newer commits touch nothing the port keeps.From upstream
sharpen: back to upstream's original prompt (pstack: restore /sharpen to the original prompt, return only the rewrite cursor/plugins#729). It asks four expert questions and returns only the rewritten prompt.create-formal-verification-skill: TLA+ as the default for ordering questions in any language, generated inputs when no verifier supports the language (fix(pstack): add TLA+ default and no-verifier fallback to create-formal-verification-skill cursor/plugins#721), and a recorded coverage list and sync commit in the generated skill. Its hand-off now points users to/maintain-formal-verification-skill.maintain-formal-verification-skill: new (pstack: add maintain-formal-verification-skill cursor/plugins#716). It brings a project's formal verification back in line after code changes that skipped the check, and says whether each failure is drift in the verification or a bug in the code.Conflict resolved
setup-pstack/SKILL.md: upstream's only change was a new step offering a formal verification skill (pstack: offer formal verification in setup, sync help and guide cursor/plugins#715). The rest of upstream's side of the conflict was its own Cursor version of this skill, which the port replaces. I kept the port's version and added the offer as step 7, worded the port's way: read~/.agents/pstack/skills/create-formal-verification-skill/SKILL.mdand follow it, instead of invoking the skill wherever Cursor installed pstack.Ported
maintain-formal-verification-skill(separate commit): it finds and updates a project-local verify skill, so it gets thepstack-harnesspointer, whose rules say where to search for project skills in Claude Code and Codex. It is user-only, so it gets the Codex policy file. It is added toSKILLSinport/install.sh. The README now lists each verification skill next to its maintain skill, so "Keeping that skill accurate" sits under the skill it refers to again.Proof
install_test.shpass, andcheck.pyreports 0 problems across 54 pstack skills.port/smoke/smoke.py. It tests the installed copy in~/.agents/pstackand needs Codex, which isn't on this machine. Its scenarios don't coversharpen,setup-pstack, or either formal verification skill.