Who it is forA developer who edited CYPRESS files in their repository and needs to reinstall or update the method without losing those edits.
The problemRe-running an installer can silently overwrite local changes to instruction files, so the team loses decisions made in those files.
The outcomeAny file that differed from the new version is kept beside it as a timestamped copy, and matching files are left alone.
What you need first
- bash
- Python 3.14 or newer on PATH
- git, to clone the repository
- Claude Code or another supported coding tool, with a session rooted at your project
Steps
./Cypress/install.sh claude-code --project-dir /path/to/your/project- Look in the project for timestamped copies of any file that differed.
- Compare each copy with its replacement and move your edits into the new file by hand.
- Check .cypress/seed.json for the version and options of the install.
Prompt for your agent
In the Cypress repo, re-run the claude-code installer against <project-path>. Expected output: a list of files replaced, each with a timestamped copy of the old version. Verify that .cypress/seed.json shows the new install stamp and that each timestamped copy still exists.
Caveat. The README says the install does not merge files, so any edits in the timestamped copies must be moved into the new versions by you.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for llopresto87/Cypress and "Update the workflow without losing your edited files"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer