update-sf

Update the SaaS Factory toolbox by pulling from main and replacing .claude/.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/marcoapereirav-arch/nvision-saas-factory --skill update-sf-marcoapereirav-arch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-sf
Source: https://github.com/marcoapereirav-arch/nvision-saas-factory/tree/main/saas-factory/.claude/skills/update-sf
Command: npx skills add https://github.com/marcoapereirav-arch/nvision-saas-factory --skill update-sf-marcoapereirav-arch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill updates the SaaS Factory development toolbox (.claude/) to the latest version available, ensuring your project stays current.

Core Features & Use Cases

  • Alias discovery: locates the saas-factory alias in your shell configuration to determine the repo path.
  • Version sync: performs a git pull to fetch the latest changes from main.
  • Toolbox replacement: replaces the .claude/ toolbox in the project while preserving user-specific files (CLAUDE.md, .mcp.json, and src).
  • Use Case: you want to apply a new release across all projects without touching your source code.

Quick Start

Update SaaS Factory to the latest version in your project.

Frequently Asked Questions about update-sf

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

FAQPage Schema
How do I update the SaaS Factory toolbox in my project without overwriting source files?▼

Updating the SaaS Factory toolbox replaces the .claude/ directory by pulling from main while preserving your CLAUDE.md, .mcp.json, and src files. It locates the saas-factory alias in your shell config to determine the repository path before refreshing the toolbox.

What is the process for syncing the SaaS Factory development toolbox to the latest version?▼

Syncing the SaaS Factory development toolbox involves discovering the saas-factory alias, performing a git pull from main, and replacing the .claude/ toolbox. This ensures your project stays current with the latest version while keeping user-specific files intact.

Does updating the .claude/ toolbox modify my CLAUDE.md and .mcp.json configurations?▼

No, updating the .claude/ toolbox does not modify your CLAUDE.md or .mcp.json configurations. The update process specifically preserves these user-specific files alongside your src directory while replacing only the development toolbox components.

How does alias discovery work when locating the SaaS Factory repository path?▼

Alias discovery works by scanning your shell configuration for the saas-factory alias to determine the repository path. This allows the update tool to locate the correct repository and perform a git pull to fetch the latest changes from main.

Can I apply a new SaaS Factory release across multiple projects without touching my source code?▼

Yes, you can apply a new SaaS Factory release across multiple projects without touching your source code. The update process replaces the .claude/ toolbox while preserving CLAUDE.md, .mcp.json, and src files, ensuring your source code remains completely intact.

What are the limitations of using the SaaS Factory update tool for version control?▼

The SaaS Factory update tool is limited to refreshing the .claude/ toolbox by pulling from main. It requires a saas-factory alias in your shell configuration and does not manage version control for your actual project files or source code.