skills.rest
mbaker95
mbaker95COMMUNITY
Explore all skills by this author →
GitHub

update-nanodex

Synchronize a forked repository with upstream NanoDex changes while preserving local modifications.

Updated Mar 11, 2026
Search Tags:#git#codebase#merge#sync#upstream#fork
One-click install
npx skills add https://github.com/mbaker95/nanodex --skill update-nanodex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-nanodex
Source: https://github.com/mbaker95/nanodex/tree/main/.agents/skills/update-nanodex
Command: npx skills add https://github.com/mbaker95/nanodex --skill update-nanodex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users integrate updates from the main NanoDex repository into their own customized forks, ensuring their local version stays current while preserving their unique modifications.

Core Features & Use Cases

  • Upstream Sync: Fetches and merges changes from the upstream remote.
  • Conflict Resolution: Guides the user through resolving merge conflicts to protect local customizations.
  • Verification: Includes steps to check the working tree and run build checks post-merge.
  • Use Case: A developer has forked NanoDex and made several custom changes. They want to pull in the latest features and bug fixes from the original repository without losing their work.

Quick Start

Use the update-nanodex skill to synchronize your local repository with the upstream NanoDex changes.

Frequently Asked Questions about update-nanodex

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync a fork with upstream changes without losing local modifications?▼

To merge upstream changes into a forked repository, the Skill fetches new commits from the upstream remote, integrates them via merging or cherry-picking, and helps resolve conflicts to preserve your local customizations.

What is the best way to resolve merge conflicts when pulling upstream commits into a customized fork?▼

The best way to resolve merge conflicts when pulling upstream commits is to follow the Skill's guided conflict resolution process, which inspects commits and integrates changes selectively to protect your local codebase customizations.

Can I cherry-pick specific upstream commits instead of merging the entire upstream branch?▼

Yes, the Skill supports cherry-picking specific upstream commits instead of performing a full merge, allowing you to inspect fetched commits and selectively integrate changes into your forked repository.

How do I verify my codebase after integrating upstream changes?▼

You verify your codebase after integrating upstream changes by checking the working tree status and running build checks, which the Skill includes as post-merge steps to ensure the merged code functions correctly.

Why does my upstream sync fail when I have uncommitted local changes in my fork?▼

Your upstream sync might fail with uncommitted local changes because the merge process requires a clean working tree. The Skill inspects the working tree before fetching and merging to prevent integration conflicts.

Related Skills

Explore More Software Engineering Skills→
youssif-mohamed1youssif-mohamed1
1

speckit-git-remote

Extract GitHub owner and repository from a Git origin remote URL.

Community
Basic
bonitasoft-presalesbonitasoft-presales

bonita-deploy-local

Automate local Bonita server deployment with Docker Compose and Maven.

Official
Intermediate
OutlineDrivenOutlineDriven
5

pr-merge-base

Merge multiple pull requests into the default branch with ordered application and conflict handling.

Official
Advanced
shaun0927shaun0927

git-master

Automate atomic commits, interactive rebasing, and branch management in Git.

Community
Advanced