Skip to content

armgit / hypit

Public Imported from GitHub
0

Clone any viral video with AI agents. Not just a script, the whole workflow: swap the face, the words, the B-roll, ship 100 variants in one command, and get your 100M views.

fix(skill): sync repository without updating installed skill

rpone657130a35ed6
diff --git a/skills/hypit/SKILL.md b/skills/hypit/SKILL.md
index db5ca1ad..c6e0c449 100644
--- a/skills/hypit/SKILL.md
+++ b/skills/hypit/SKILL.md
@@ -22,19 +22,13 @@ git pull --ff-only origin main
```
This is a whole-repository update: it refreshes the CLI, packages, services, examples, docs and Skill
-source together. Do not treat an installed Skill update as a substitute for pulling the checkout.
-After the checkout is current, refresh the installed global Skill as well:
-
-```bash
-npx --yes skills update hypit --global --yes
-```
-
-Run the repository pull and installed Skill refresh once per conversation, do not repeat them for later
-turns, and then continue with the current request using the current checkout and refreshed Skill. Do
+source together. Do not run a Skill package-manager update or overwrite the installed Skill from this
+startup path. Run the repository pull once per conversation, do not repeat it for later turns, and then
+continue with the current request using the current checkout. Do
not reset or overwrite local changes: if `git pull --ff-only origin main` cannot fast-forward, stop and
report the sync conflict. If no contributor checkout is selected, there is no local repository to pull;
-still run the global Skill refresh and report that only the installed Skill was updated. If either
-operation cannot complete because the network or CLI is unavailable, report that the latest state could
+use the currently installed Skill without attempting a Skill update. If the repository pull cannot
+complete because the network or Git is unavailable, report that the latest state could
not be confirmed before proceeding; never pretend the repository is current.
**Run the route to the end without stopping.** There is one thing worth interrupting the author for;
diff --git a/skills/hypit/references/host-setup.md b/skills/hypit/references/host-setup.md
index a20700e7..b962ab86 100644
--- a/skills/hypit/references/host-setup.md
+++ b/skills/hypit/references/host-setup.md
@@ -182,14 +182,12 @@ Updates to an installed, published Distribution remain an explicit package-manag
```text
npm outdated --global hypit
npm update --global hypit
-npx skills update --global
```
Use `hypit --version` to report the installed Distribution. Check npm only when the user asks about
updates or during deliberate environment maintenance; do not add a Distribution registry request to
-every route. The Hypit Skill itself is different: its `SKILL.md` requires one
-`npx --yes skills update hypit --global --yes` refresh the first time the Skill is loaded in each new
-conversation.
+every route. The Hypit Skill is synchronized from the contributor checkout, when one is selected,
+by the session-initialization `git pull --ff-only origin main` step.
Do not run those npm commands for a contributor checkout; update it through its repository workflow.
After updating Hypit, stop an idle Runtime Worker before the next Build so the next process loads the