update
Skill2 starsChanged 8 months agoMITView on GitHub
Update NanoClawbster from upstream. Fetches latest changes, merges with your customizations and skills, runs migrations. Triggers on \"update\", \"pull upstream\", \"sync with upstream\", \"get latest changes\".
- Deletes or force-pushes
65 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- finolabs/finolabs-vibecodetheir own version, first seen Nov 16, 2026
- patrickjaja/claude-desktop-extratheir own version, first seen Nov 15, 2026
- FYClamityDestiny/vettedtheir own version, first seen Nov 15, 2026
- shivasaini04/nanocrewedited, first seen Nov 15, 2026
- finolabs/vibecodetheir own version, first seen Nov 15, 2026
- onetapstudiogames/1f3d9-citylifetheir own version, first seen Nov 13, 2026
Used with
Projects with it also use pause, end and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
kennethleungtySkillpause
Pause — stop the music (alias for /stop)
Also in 4 projects that use this
torarnvSkillend
Wrap up a work session. Updates memory files, logs decisions and lessons, appends to the session log.
Also in 3 projects that use this
MicrosoftSkillcreate
Also in 4 projects that use this
bitwize-music-studioSkilltutorial
Provides interactive guided album creation for new users. Use when the user is new to the plugin or asks for a walkthrough of the album creation process.
Also in 3 projects that use this
MicrosoftSkillhelp
Entry point for the MedImageInsight plugin, covering the getting-started walkthrough, how the skills work, what MI2 is, and troubleshooting.
Also in 8 projects that use this
jholhewresSkillbackup
Backup and restore — files, databases, and system backups
Also in 3 projects that use this
- +1 more from microsoft
Other versions65 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- shivasaini04/nanocrew★ 496% same
Wrote their own version · 64
- anthropics/knowledge-work-plugins★ 36ksame name
- Q00/ouroboros★ 6.4ksame name
- vellum-ai/vellum-assistant★ 1.5ksame name
- patrickjaja/claude-desktop-extra★ 761same name
- me2resh/apexyard★ 542same name
- daloopa/investing★ 488same name
- TokenRollAI/cc-plugin★ 483same name
- egregore-labs/egregore★ 293same name
- k1p1l0/claude-telegram-supercharged★ 144same name
- kv0906/pm-kit★ 138same name
54 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-parallelSkill
- add-telegram-swarmSkill
- convert-to-apple-containerSkill
- customizeSkill
- debugSkill
- get-qodo-rulesSkill
- qodo-pr-resolverSkill
- setupSkill
- x-integrationSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
22 rules. 0 are common, 11 are distinctive, and 11 are very specific to this project.
0
Common
Most of the 63 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
UX Note: Use AskUserQuestion for all user-facing questions.
- Distinctive: line 16
Check that the skills system is initialized:
- Very specific: line 22
If NOT_INITIALIZED: Run initSkillsSystem() first:
- Distinctive: line 28
Check for uncommitted git changes:
- Distinctive: line 38
Run the fetch script:
- Distinctive: line 57
Run the preview to show what will change:
- Very specific: line 68
If conflictRisk is non-empty: "These files have skill modifications and may conflict: {list}"
- Very specific: line 69
If customPatchesAtRisk is non-empty: "These custom patches may need re-application: {list}"
- Very specific: line 70
If filesDeleted is non-empty: "{N} files will be removed"
- Very specific: line 74
Use AskUserQuestion: "Apply this update?" with options:
- Very specific: line 78
If cancelled, clean up the temp dir (rm -rf <TEMP_DIR>) and stop.
- Very specific: line 101
Read the file — it contains conflict markers (<<<<<<<, =======, >>>>>>>)
- Very specific: line 102
Check if there's an intent file for this path in any applied skill (e.g., .claude/skills/<skill>/modify/<path>.intent.md)
- Distinctive: line 103
Use the intent file and your understanding of the codebase to resolve the conflict
- Distinctive: line 104
Write the resolved file
- Distinctive: line 106
After resolving all conflicts:
- Distinctive: line 118
Run migrations between the old and new versions:
- Distinctive: line 132
Run build and tests:
- Distinctive: line 148
Remove the temp directory:
- Distinctive: line 164
Merge conflicts in many files: Consider whether the user has heavily customized core files.
- Very specific: line 166
Build fails after update: Check if package.json dependencies changed.
- Very specific: line 168
Rollback: If something goes wrong after applying but before cleanup, the backup is still in .nanoclawbster/backup/.
“Common” is measured: kept by at least 6 in 10 of the 63 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Update NanoClawbster
Pull upstream changes and merge them with the user's installation, preserving skills and customizations. Scripts live in .claude/skills/update/scripts/.
Principle: Handle everything automatically. Only pause for user confirmation before applying changes, or when merge conflicts need human judgment.
UX Note: Use AskUserQuestion for all user-facing questions.
1. Pre-flight
Check that the skills system is initialized:
test -d .nanoclawbster && echo "INITIALIZED" || echo "NOT_INITIALIZED"If NOT_INITIALIZED: Run initSkillsSystem() first:
npx tsx -e "import { initNanoclawDir } from './skills-engine/init.js'; initNanoclawDir();"Check for uncommitted git changes:
git status --porcelainIf there are uncommitted changes: Warn the user: "You have uncommitted changes. It's recommended to commit or stash them before updating. Continue anyway?" Use AskUserQuestion with options: "Continue anyway", "Abort (I'll commit first)". If they abort, stop here.
2. Fetch upstream
Run the fetch script:
./.claude/skills/update/scripts/fetch-upstream.shParse the structured status block between <<< STATUS and STATUS >>> markers. Extract:
TEMP_DIR— path to extracted upstream filesREMOTE— which git remote was usedCURRENT_VERSION— version from localpackage.jsonNEW_VERSION— version from upstreampackage.jsonSTATUS— "success" or "error"
If STATUS=error: Show the error output and stop.
If CURRENT_VERSION equals NEW_VERSION: Tell the user they're already up to date. Ask if they want to force the update anyway (there may be non-version-bumped changes). If no, clean up the temp dir and stop.
3. Preview
Run the preview to show what will change:
npx tsx scripts/update-core.ts --json --preview-only <TEMP_DIR>This outputs JSON with: currentVersion, newVersion, filesChanged, filesDeleted, conflictRisk, customPatchesAtRisk.
Present to the user:
- "Updating from {currentVersion} to {newVersion}"
- "{N} files will be changed" — list them if <= 20, otherwise summarize
- If
conflictRiskis non-empty: "These files have skill modifications and may conflict: {list}" - If
customPatchesAtRiskis non-empty: "These custom patches may need re-application: {list}" - If
filesDeletedis non-empty: "{N} files will be removed"
4. Confirm
Use AskUserQuestion: "Apply this update?" with options:
- "Yes, apply update"
- "No, cancel"
If cancelled, clean up the temp dir (rm -rf <TEMP_DIR>) and stop.
5. Apply
Run the update:
npx tsx scripts/update-core.ts --json <TEMP_DIR>Parse the JSON output. The result has: success, previousVersion, newVersion, mergeConflicts, backupPending, customPatchFailures, skillReapplyResults, error.
If success=true with no issues: Continue to step 7.
If customPatchFailures exist: Warn the user which custom patches failed to re-apply. These may need manual attention after the update.
If skillReapplyResults has false entries: Warn the user which skill tests failed after re-application.
6. Handle conflicts
If backupPending=true: There are unresolved merge conflicts.
For each file in mergeConflicts:
- Read the file — it contains conflict markers (
<<<<<<<,=======,>>>>>>>) - Check if there's an intent file for this path in any applied skill (e.g.,
.claude/skills/<skill>/modify/<path>.intent.md) - Use the intent file and your understanding of the codebase to resolve the conflict
- Write the resolved file
After resolving all conflicts:
npx tsx scripts/post-update.tsThis clears the backup, confirming the resolution.
If you cannot confidently resolve a conflict: Show the user the conflicting sections and ask them to choose or provide guidance.
7. Run migrations
Run migrations between the old and new versions:
npx tsx scripts/run-migrations.ts <CURRENT_VERSION> <NEW_VERSION> <TEMP_DIR>Parse the JSON output. It contains: migrationsRun (count), results (array of {version, success, error?}).
If any migration fails: Show the error to the user. The update itself is already applied — the migration failure needs manual attention.
If no migrations found: This is normal (most updates won't have migrations). Continue silently.
8. Verify
Run build and tests:
npm run build && npm testIf build fails: Show the error. Common causes:
- Type errors from merged files — read the error, fix the file, retry
- Missing dependencies — run
npm installfirst, retry
If tests fail: Show which tests failed. Try to diagnose and fix. If you can't fix automatically, report to the user.
If both pass: Report success.
9. Cleanup
Remove the temp directory:
rm -rf <TEMP_DIR>Report final status:
- "Updated from {previousVersion} to {newVersion}"
- Number of files changed
- Any warnings (failed custom patches, failed skill tests, migration issues)
- Build and test status
Troubleshooting
No upstream remote: The fetch script auto-adds upstream pointing to https://github.com/qwibitai/nanoclawbster.git. If the user forked from a different URL, they should set the remote manually: git remote add upstream <url>.
Merge conflicts in many files: Consider whether the user has heavily customized core files. Suggest using the skills system for modifications instead of direct edits, as skills survive updates better.
Build fails after update: Check if package.json dependencies changed. Run npm install to pick up new dependencies.
Rollback: If something goes wrong after applying but before cleanup, the backup is still in .nanoclawbster/backup/. Run:
npx tsx -e "import { restoreBackup, clearBackup } from './skills-engine/backup.js'; restoreBackup(); clearBackup();"Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

