Run any Skill in Manus with one click

update-hub

Stars18

Forks1

UpdatedJuly 2, 2026 at 18:20

Pull the latest template improvements into this hub — fetch the template recorded in .hub-meta.yml, diff since the recorded commit, re-apply with this hub's values, verify. Use when asked to update or upgrade the hub from its template.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

PakhomovAlexander

PakhomovAlexander/project-hub

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	update-hub
description	Pull the latest template improvements into this hub — fetch the template recorded in .hub-meta.yml, diff since the recorded commit, re-apply with this hub's values, verify. Use when asked to update or upgrade the hub from its template.

Update the hub from its template

This hub was generated from a Project Hub template; .hub-meta.yml at the hub root records which one and at what commit. The update procedure lives in the template repo (its UPDATE.md), not here — so every hub, however old, runs the latest version of it. This skill just gets you there:

Read .hub-meta.yml (no file? look for a generated from project-hub@<sha> stamp at the bottom of README.md, and ask the user for the template URL).
Clone template.url into a scratch directory — a full clone, the update diffs against the recorded sha.
Open UPDATE.md at the root of that clone and follow it top to bottom. It defines the three-way merge: what you may update freely (machinery), what you must never overwrite (this hub's own docs), and the verify + provenance-bump steps.
Done = the hub's scripts/verify.sh passes, .hub-meta.yml points at the new template sha, and your summary lists every applied / merged / skipped change.

More from this repository

same repository

adr

PakhomovAlexander/project-hub

Record an architecture decision as a new ADR — numbered, honest about the rejected options, and wired into the index, the plan, and the invariants. Use when a significant decision was just made or needs recording.

2026-07-0218

onboard-repo

PakhomovAlexander/project-hub

Link a new repo into the hub and document it — manifest entry, symlink, Tier-1 reference doc with the dev loop, catalog row. Use when the project grows a repo or an existing repo isn't wired in yet.

2026-07-0218

resume

PakhomovAlexander/project-hub

Pick up an in-flight workstream cold — load its design doc, verify its claimed state against reality, and continue from the "resume here" list. Use when returning to interrupted work or taking over someone else's stream.

2026-07-0218

tracker

PakhomovAlexander/project-hub

Refresh docs/tracker.md — the live status board — so it is true right now. Use at the start or end of a work session, when the session brief flags the snapshot as stale, or after anything lands.

2026-07-0218

verify

PakhomovAlexander/project-hub

Self-check the hub — leftover placeholders, broken internal links, links into gitignored repos/, non-executable hooks, stale tracker. Run before pushing doc changes or after any bulk edit.

2026-07-0218

name	update-hub
description	Pull the latest template improvements into this hub — fetch the template recorded in .hub-meta.yml, diff since the recorded commit, re-apply with this hub's values, verify. Use when asked to update or upgrade the hub from its template.

Update the hub from its template

Read .hub-meta.yml (no file? look for a generated from project-hub@<sha> stamp at the bottom of README.md, and ask the user for the template URL).
Clone template.url into a scratch directory — a full clone, the update diffs against the recorded sha.
Open UPDATE.md at the root of that clone and follow it top to bottom. It defines the three-way merge: what you may update freely (machinery), what you must never overwrite (this hub's own docs), and the verify + provenance-bump steps.
Done = the hub's scripts/verify.sh passes, .hub-meta.yml points at the new template sha, and your summary lists every applied / merged / skipped change.