From servicenow
Reviewing, analyzing, and comparing ServiceNow update sets before promotion. Shows changes, risks, dependencies, and conflicts. Use when the user mentions update sets, customizations, promotion, code review, change tracking, pre-deployment review, sys_update_xml, customer updates, "what changed in this update set," or "is this safe to promote."
npx claudepluginhub kylburns89/servicenow-claude-plugins --plugin pluginThis skill is limited to using the following tools:
Review, analyze, and compare update sets before promotion. See `references/update-set-fields.md` for update types, risk categories, and pre-promotion checklist fields.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Review, analyze, and compare update sets before promotion. See references/update-set-fields.md for update types, risk categories, and pre-promotion checklist fields.
Get an overview of update sets by state with change counts.
Progress checklist (copy into your response):
- [ ] List update sets by state
- [ ] Get change counts for each
- [ ] Summarize by developer and state
list_update_sets(state="in progress", limit=20)
list_update_sets(state="complete", limit=20)
list_update_set_changes(update_set_sys_id="<sys_id>", limit=1)
Examine all changes in an update set, categorize by type, and flag risks.
Progress checklist:
- [ ] Get update set details
- [ ] List all customer updates
- [ ] Categorize changes by type
- [ ] Flag risky changes (ACLs, script includes, schema changes)
- [ ] Summarize findings with risk assessment
get_update_set(sys_id="<update_set_sys_id>")
list_update_set_changes(update_set_sys_id="<update_set_sys_id>", limit=100)
references/update-set-fields.md for risk categories:
Find overlapping records and potential conflicts between two update sets.
Progress checklist:
- [ ] Get changes for update set A
- [ ] Get changes for update set B
- [ ] Find overlapping records (same target name/table)
- [ ] Identify potential conflicts
- [ ] Report overlap and conflict details
list_update_set_changes(update_set_sys_id="<set_a_sys_id>", limit=100)
list_update_set_changes(update_set_sys_id="<set_b_sys_id>", limit=100)
target_name modified in both setsValidate an update set is safe to promote using a structured checklist.
Progress checklist:
- [ ] Verify state is "complete"
- [ ] Check for Default update set entries mixed in
- [ ] Scan for test/personal artifacts
- [ ] Check for incomplete references
- [ ] Flag risky change types
- [ ] Generate promotion readiness report
get_update_set(sys_id="<update_set_sys_id>")
list_update_set_changes(update_set_sys_id="<update_set_sys_id>", limit=100)
complete (not in progress)ignore state are intentionally excluded from promotion — don't flag them.sys_update_xml table stores the actual XML payload of each change. Query it for detailed diffs.order_by="-sys_created_on" to see the most recent update sets first.references/update-set-fields.md for the full list of change types and risk categories.