update-set-workflow

Name: update-set-workflow
Availability: InStock
Author: serac

Create or activate named ServiceNow Update Sets to track development changes.

77|23|Updated Jul 16, 2025

Search Tags:#automation #workflow #deployment #dev-ops #servicenow #change-tracking #update-set

Ready to run

npx skills add https://github.com/serac-labs/serac --skill update-set-workflow-serac-labs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-set-workflow
Source: https://github.com/serac-labs/serac/tree/main/packages/opencode/src/bundled-skills/update-set-workflow
Command: npx skills add https://github.com/serac-labs/serac --skill update-set-workflow-serac-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update Sets provide mandatory tracking for ServiceNow development changes to enable reliable deployment.

Core Features & Use Cases

Create or switch to a named Update Set before making changes to ensure all work is captured.
Track a broad range of ServiceNow changes (tables, scripts, business rules, UI policies, workflows, etc.) and promote them between instances.
Follow recommended lifecycle and naming conventions, and use MCP Tools (snow_update_set_create, snow_update_set_current, snow_update_set_switch, snow_update_set_complete, snow_ensure_active_update_set) to manage updates.

Quick Start

Create or activate a named Update Set and begin tracking all changes before you start development.

Frequently Asked Questions about update-set-workflow

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

FAQPage Schema

How do I automate ServiceNow update set workflows for deployment?▼

You can automate ServiceNow update set workflows by using this skill to apply mandatory change tracking, create or activate named update sets, follow naming conventions, and manage the lifecycle before deployment.

What is the best way to track ServiceNow development changes across environments?▼

The best way to track ServiceNow development changes across environments is to create or switch to a named update set before making changes, ensuring all feature work, bug fixes, and configuration updates are captured for reliable deployment.

How do I create and switch to a named update set before starting development?▼

To create and switch to a named update set, you use MCP Tools like snow_update_set_create and snow_update_set_switch to activate the set, ensuring all subsequent ServiceNow changes are automatically captured.

What types of ServiceNow changes can I track and promote between instances?▼

You can track and promote a broad range of ServiceNow changes between instances, including tables, scripts, business rules, UI policies, workflows, and configuration updates.

How do I manage the update set lifecycle and mark development work as complete?▼

You manage the update set lifecycle and mark work as complete by utilizing MCP Tools such as snow_update_set_complete to finalize the update set and prepare it for export and deployment.