iwe-update

Update IWE installations and summarize version changes with conflict guidance.

44|125|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/TserenTserenov/FMT-exocortex-template --skill iwe-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iwe-update
Source: https://github.com/TserenTserenov/FMT-exocortex-template/tree/main/.claude/skills/iwe-update
Command: npx skills add https://github.com/TserenTserenov/FMT-exocortex-template --skill iwe-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps a user's IWE (FMT-exocortex-template) installation up to date while explaining what changed and how updates interact with local customizations, preventing lost context and unexpected breakage.

Core Features & Use Cases

  • Preview and Apply Updates: Run the template's update script in preview or apply mode, summarize the upstream version delta, and report files changed.
  • Human-friendly Changelog Explanation: Parse CHANGELOG.md and turn technical entries into 1–3 user-focused bullets describing benefits, behavioral changes, and fixes.
  • Compatibility Analysis and Conflict Guidance: Detect extension and params.yaml differences, identify 3-way merge conflicts (e.g., CLAUDE.md), and guide the user through resolution and parameter updates.
  • Use Case: A user with site-specific extensions wants to safely pull a new IWE release, understand breaking changes, and merge platform updates without losing custom behavior.

Quick Start

Ask the agent to preview and explain available IWE updates, review compatibility with your extensions and params, and then apply the update with guided conflict resolution.

Frequently Asked Questions about iwe-update

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

FAQPage Schema
How do I safely update my IWE template repository without losing local customizations?

To safely update IWE, run the update.sh script in preview mode to check upstream changes, inspect extension and params.yaml differences, then apply the update with guided 3-way merge conflict resolution to preserve local customizations.

What is the best way to understand IWE changelog updates before applying them?

Parsing the CHANGELOG.md file translates technical update entries into 1-3 user-focused bullets that summarize benefits, behavioral changes, and fixes, helping you understand IWE changelog updates before applying them to your repository.

How do I resolve merge conflicts when pulling new IWE releases into my customized repository?

Resolving IWE merge conflicts involves detecting 3-way merge differences in files like CLAUDE.md, identifying extension and params.yaml incompatibilities, and following guided user decisions to merge platform updates without losing custom behavior.

Can I preview IWE upstream changes before committing to a full template update?

Yes, you can preview IWE upstream changes by executing the update script in preview mode, which summarizes the version delta and reports files changed before you commit to applying the full template update to your local repository.

Does updating IWE break existing extensions and params.yaml configurations?

Updating IWE can introduce compatibility issues with existing extensions and params.yaml configurations, but the update process detects these differences, identifies potential conflicts, and guides you through parameter additions and resolutions to prevent breakage.